Skip to main content
Glama
eLyiN

Codex Bridge

by eLyiN
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

consult_codex_with_stdin

Pipe stdin content to Codex AI for processing with a prompt, enabling automated code analysis and batch review in CI/CD pipelines.

Instructions

Consult Codex with stdin content piped to prompt - pipeline-friendly execution.

Similar to 'echo "content" | codex exec "prompt"' - combines stdin with prompt.
Perfect for CI/CD workflows where you pipe file contents to the AI.

Args:
    stdin_content: Content to pipe as stdin (e.g., file contents, diff, logs)
    prompt: The prompt to process the stdin content
    directory: Working directory (required)
    format: Output format - "text", "json", or "code" (default: "json")
    timeout: Optional timeout in seconds (overrides env var, recommended: 60-120)
    
Returns:
    Formatted response based on format parameter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stdin_contentYes
promptYes
directoryYes
formatNojson
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior2/5

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

No annotations provided; description only mentions timeout and pipeline nature, lacking disclosure on permissions, side effects, or error handling.

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?

Compact structure with summary, analogy, use case, and parameter list; no wasted 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?

Covers parameters and use case well, but lacks detail on return value variations beyond format parameter and error conditions.

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

Parameters5/5

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

With 0% schema coverage, description adds clear purpose for each parameter, including examples and recommended timeout range, far exceeding minimum.

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?

Describes specific verb 'Consult Codex' with stdin piping, clearly distinguishes from siblings via pipeline-friendly execution and analogy to 'echo | codex exec'.

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?

States perfect for CI/CD workflows and gives usage analogy, but does not explicitly mention when not to use or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eLyiN/codex-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server