Skip to main content
Glama

run_gate_acknowledge

Dismiss a review gate without continuing.

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_acknowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does add one meaningful behavioral fact — the gate is closed without advancing the run — but says nothing about whether the dismissal is reversible, what terminal state the job enters, what permissions are required, or whether the gate can be re-raised.

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?

One short front-loaded sentence with zero padding — the core action comes first. It is efficient, though it sits close to the edge of being under-specified rather than genuinely concise.

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?

The tool is simple (one parameter), but with no annotations, no output schema, and no parameter descriptions, the definition is the only source of behavioral information and it does not cover post-dismissal state, reversibility, or error behavior. An agent could call it but could not predict the consequences.

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% and the single required parameter job_id is never mentioned. The name is fairly self-explanatory, but the description adds no meaning about format, whether it accepts a gate identifier versus a job identifier, or what happens with an invalid or already-dismissed job.

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 gives a specific verb ('Dismiss') and resource ('a review gate'), plus a scope qualifier ('without continuing') that implicitly separates it from the approving sibling run_gate_approve. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

The phrase 'without continuing' hints at the choice between dismissing and letting the gate proceed, which implies usage context. However, there is no explicit when-to-use, when-not-to-use, or named alternative (run_gate_approve, run_cancel), so the agent must infer the routing decision.

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