Skip to main content
Glama

codex_respond

Destructive

Respond to pending guidance or review requests by submitting a decision, approval, or denial, including proposal hashes for file approvals.

Instructions

Answer guidance or review requests. Typed decisions apply only to ask_parent. Approvals need human/relay; file accepts need proposal_hash. Denials need no human.

Input Schema

NameRequiredDescriptionDefault
responseYes
request_idNoPending request id, not an operation key
proposal_hashNoRequired for file_approval accept: the hash displayed with the reviewed proposal
pending_request_idNoAlias of request_id

Output Schema

NameRequiredDescriptionDefault
okYes
result_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag a destructive, non-idempotent, open-world mutation. The description adds authorization context—human/relay for approvals, proposal_hash for file accepts, no human for denials—and clarifies decision authority. It still leaves 'human/relay' and the destructive consequences undefined.

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

Conciseness4/5

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

Four short sentences, purpose first, then constraints; no filler. The telegraphic phrasing ('human/relay', 'ask_parent') makes it dense but still compact.

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

Completeness3/5

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

Output schema exists, so return values need not be explained. For a destructive mutation with a nested decision object, the description covers key approval/denial conditions but is thin on workflow mechanics and what 'human/relay' entails.

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 75% and already documents request_id, proposal_hash, pending_request_id, and response.decision. The description adds a constraint on typed decisions (ask_parent only) and reinforces proposal_hash for file accepts, but adds little beyond the schema for request identifiers.

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

Purpose4/5

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

States a specific verb ('Answer') and resource ('guidance or review requests'), so the agent knows this handles responses to pending requests. It does not explicitly differentiate from siblings like codex_requests or codex_send, so sibling selection still requires inference.

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?

Gives conditional context: typed decisions only for ask_parent, approvals need human/relay, file accepts need proposal_hash, denials need no human. However, it does not name alternative tools or spell out when to choose this over codex_requests or codex_send.

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