Skip to main content
Glama

submit_review

Submit a Codex review for a candidate commit with pass/fail per criterion and actionable issues, enabling assessment without serving as human merge approval.

Instructions

Submit Codex review: one pass/fail per criterion, plus actionable issues. Not human merge approval.

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": {
      "run_id": "<run_id>",
      "candidate_commit": "<candidate_commit>",
      "decision": "<decision>",
      "criteria": "<criteria>",
      "issues": "<issues>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "submit_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuesYes
run_idYes
criteriaYes
decisionYes
idempotency_keyYes
candidate_commitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation. It clarifies the semantics of the review payload but says nothing about what the call changes, whether re-submissions are allowed, how idempotency_key affects duplicate submissions, or what a failure response looks like.

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 short sentences, front-loaded with the action and followed by the key disambiguation. No filler or redundant restatement of the tool name.

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

Completeness2/5

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

For a six-parameter required-payload mutation with no annotations and no output schema, the description is far too thin: it does not explain parameter formats, failure modes, or whether the decision value interacts with the per-criterion results. Only the core intent and the non-approval caveat are covered.

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

Parameters2/5

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

Schema description coverage is 0% across 6 required parameters, so the description must compensate and largely does not. "Criteria" and "issues" are loosely implied by the pass/fail framing, but run_id, candidate_commit, decision, and especially idempotency_key receive no explanation of expected format or semantics.

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?

The description names a specific verb and resource ("Submit Codex review") and states what the payload conveys: one pass/fail per criterion plus actionable issues. It also rules out a likely misinterpretation ("Not human merge approval"), so an agent can distinguish it from an approval action, though it does not name a specific sibling tool.

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

Usage Guidelines3/5

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

"Not human merge approval" gives a useful when-not signal and implies this is the automated review path, but there is no positive guidance on when to call it versus siblings such as revise_task or submit_task, nor any stated prerequisites (e.g., that a run must exist).

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