Skip to main content
Glama
Sign In
codex-mcp-bridge

codex-mcp-bridge

by hampsterx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Structured Output

structured
Read-only

Generates JSON responses conforming to a provided JSON Schema for data extraction, classification, or other machine-parseable output tasks.

Instructions

Generate a JSON response conforming to a provided JSON Schema. Use for data extraction, classification, or any task needing machine-parseable output.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>",
      "schema": "<schema>"
    },
    "name": "structured"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoFile paths to include as context (text only, no images). Supports line ranges: 'path:start-end' (e.g. 'src/lib.rs:900-950').
modelNoModel to use (e.g. o3, gpt-4.1)
promptYesWhat to generate or extract
schemaYesJSON Schema the response must conform to (as a JSON string)
timeoutNoTimeout in milliseconds (default: 60000)
workingDirectoryNoWorking directory for file paths

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds that it generates a JSON response, but does not elaborate on behavior like error handling or idempotency. With annotations doing heavy lifting, the description is adequate but not exceptional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the core action followed by use cases. No redundant or missing words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 6 parameters (2 required) and no output schema, the description covers the essential function and use cases. It could hint at return value more explicitly, but 'Generate a JSON response' suffices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions. The tool description does not add additional meaning beyond what the schema already provides, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it generates JSON based on a provided schema, naming specific use cases like data extraction and classification. It distinguishes from sibling tools (codex, search) by emphasizing structured output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use for data extraction, classification, or any task needing machine-parseable output,' providing clear when-to-use guidance. However, it lacks explicit when-not-to-use or alternatives among siblings, but the context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools