Skip to main content
Glama

gate_check

Check a component in the signed attestation ledger before install to return an ALLOW, BLOCK, or REVIEW verdict with reasons.

Instructions

Look up a component (registry+name[,version]) in the signed attestation ledger and return the install-gate decision (ALLOW/BLOCK/REVIEW) with reasons.

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": {
      "registry": "<registry>",
      "name": "<name>"
    },
    "name": "gate_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
policyNodefault|strict|release-gate|lax|paranoid
versionNo
registryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It discloses only that this is a lookup against a 'signed attestation ledger' returning a three-state decision; it says nothing about what happens when a component is unknown, whether the call is logged, latency/caching, or auth requirements — all material for a gate that could block a deployment.

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?

A single tight sentence that front-loads the lookup and the returned decision enum with no filler. The parenthetical component-identifier notation is compact and useful, though slightly cryptic for a reader unfamiliar with the registry+name+version convention.

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?

For a four-parameter read tool with no output schema, the description covers purpose and return shape reasonably. It falls short on the policy parameter's effect and on edge-case behavior (component not found, unsigned entries), which an agent needs to interpret a REVIEW versus BLOCK result.

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 coverage is only 25%, so the description must compensate, and it partly does by showing that registry and name identify the component and that version is optional. However, it never mentions the 'policy' parameter, which is the single most consequential input because it shifts the decision thresholds — that omission leaves a real semantic gap.

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?

Names a specific verb and resource ('look up a component ... in the signed attestation ledger') and states the output shape (ALLOW/BLOCK/REVIEW with reasons). It is clearly distinct from store_summary and verify_bundle by name and by the described data source, though it does not explicitly contrast itself with either sibling.

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?

Usage is implied rather than stated: the 'install-gate decision' phrase signals a pre-install check, but the description never says when to call this instead of verify_bundle or store_summary, nor any when-not condition or prerequisite such as needing a prior attestation stored.

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

Deploy Server

Other Tools