MCP tools and resources

Tools perform explicit operations; resources provide passive context that Codex can inspect before choosing an operation.

When to use

Use resources for discovery and tools for deliberate execution or writes.

Behavior

Project tools cover manifest inspection, doctor checks, validation, canonical export, YAML import, and generated project requests.
Refresh tools explicitly fetch public ServiceGen capability and validation contracts and cache them in the workspace.
Fixed resources report current project state and cached contracts without making hidden network requests.
Resource templates expose exact diagnostic rules by SG_* code instead of asking the agent to infer remediation from a code name.

Tool families properties

Capabilities exposed as bounded MCP operations.

PropertyTypeDescription

Inspect and doctorLocal read

Discover the project and diagnose environment or cache compatibility.

Validate and exportLocal execution/write

Evaluate the trusted topology and emit canonical YAML.

ImportLocal generation

Create a modular typed Python project from canonical YAML.

GenerateRemote authorized operation

Submit validated architecture and receive a native runtime ZIP.

Refresh contractsPublic network read

Cache current ServiceGen capability and validation metadata.

Validation resources properties

Stable URIs relevant to rule-driven authoring.

PropertyTypeDescription

servicegen://workspace/current/validation-contractFixed resource

Cached versioned validation catalog and revision metadata.

servicegen://validation/rules/{code}Resource template

Exact condition and remediation for one SG_* diagnostic.

validationRuleUriDiagnostic field

Resource URI attached to an MCP validation diagnostic.

Example

1. Read the passive workspace resource.
2. Run validation explicitly.
3. Follow diagnostic.validationRuleUri for the exact rule.
4. Apply the smallest typed-model correction.
5. Validate again before export.