Skip to main content
Glama

run_gate_approve

Approve a review gate. Continuing downstream steps BILLS CREDITS — without confirm:true this only returns what continuing will cost (up to max_credits) and continues nothing. Omit block_ids to continue over ALL blocks the run processed; pass a subset to continue only those; pass [] to close the gate WITHOUT running (or billing) anything further (no confirm needed). No downstream steps → error no_continuation (use run_gate_acknowledge).

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": {
      "job_id": "<job_id>"
    },
    "name": "run_gate_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirmNo
block_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses that continuing bills credits, that without confirm:true it is a cost-preview dry run, and that it returns the error no_continuation in the no-downstream case. It does not cover authorization requirements, idempotency/reversibility of the gate approval, or the shape of the preview response beyond cost.

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?

Front-loads the action, then the billing hazard, then the parameter modes, then the error case — a sensible hazard-first ordering. It is dense and uses heavy capitalization for emphasis, which is slightly noisy but every clause carries information.

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?

For a three-parameter, no-annotation, no-output-schema mutation tool with a cost side effect, the description covers the dangerous parts: billing, dry run, parameter modes, and the failure path with a sibling redirect. Only job_id semantics and the preview response contents are left implicit.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for two of three parameters: confirm is explained as the billing/dry-run switch and block_ids is given three distinct modes including the special empty-array meaning. job_id is left unexplained, which is the only gap.

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?

States a specific verb and resource ('Approve a review gate') and immediately distinguishes itself from the sibling run_gate_acknowledge by naming it as the tool to use when there are no downstream steps. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when/when-not guidance: omit block_ids to continue over all blocks, pass a subset to continue only those, pass [] to close without running or billing, and use run_gate_acknowledge instead when no downstream steps exist. It also states that confirm is not needed for the empty-array case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources