Skip to main content
Glama

gate

Read-onlyIdempotent

Inspect the command and state for a file's named verification gate without executing it, and get the ordered work plan of checks a change owes.

Instructions

Show the command and state for a file's named verification gate; it does not execute the command. Use steps for an ordered work plan. Successful structured results include the command record and exit code.

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": {
      "path": "<path>"
    },
    "name": "gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateNoa key of atlas.yaml/gate_tools; omit it for every gate the change needs
pathYesExisting path, absolute or relative to the client directory.
changeNothe change class, when no gate is namedsource_change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.63.0
    • changedInput schema / properties / path / description
      Previous value: -"path"New value: +"Existing path, absolute or relative to the client directory."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds meaningful nuance by stating 'it does not execute the command', which prevents an agent from assuming a side effect, and notes the return content. However, it says nothing about error behavior when a gate is not defined or when the path is invalid.

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?

Three short sentences, with the core operation and the sibling exclusion front-loaded. The phrase 'Successful structured results include' is slightly awkward, but no sentence is wasted.

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?

There is no output schema, and the description compensates by naming the key returned fields (command record and exit code). For a read-only, fully-documented-parameter tool, this is nearly complete, with only failure-mode behavior left implicit.

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 description coverage is 100%, so the schema already documents path, gate, and change with defaults and semantics. The description adds only the notion of a 'named' gate, which the schema already conveys; baseline 3 is appropriate.

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 uses a specific verb and resource ('Show the command and state for a file's named verification gate') and distinguishes itself from the sibling 'steps' by naming it directly. The object ('gate') is somewhat domain-specific jargon, but the surrounding clause makes the operation clear.

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?

It gives explicit routing guidance ('Use steps for an ordered work plan'), which tells the agent when this tool is not the right choice. It does not enumerate other alternatives or state prerequisites, but the one exclusion is the most important one.

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