Skip to main content
Glama

gate

Check whether an agent meets minimum trust and security requirements before granting access to your API or service.

Instructions

B2B trust gate — check if an agent meets minimum trust and security requirements. Use this to decide whether to allow an agent to access your API or service.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name to gate-check
min_gradeNoMinimum security grade required: A, B, C, D, F (default: C)
min_trustNoMinimum trust score required (default: 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/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 burden. It implies a read-only evaluation but never states what happens on failure, whether the call is side-effect free, or what the result looks like (boolean vs. grade vs. score). For a gating decision tool with zero annotation coverage, this is a meaningful gap.

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?

Two tight sentences with the purpose front-loaded and the decision use case second. No filler, though the second sentence is somewhat redundant with the first.

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?

With no output schema and no annotations, the description should explain the return shape (pass/fail, grade, trust score) and failure semantics, since that is exactly what an agent needs to act on a gate result. It leaves the entire response contract unspecified.

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 name, min_grade, and min_trust are already documented with defaults. The description adds no additional meaning such as how min_grade and min_trust interact or what happens when they conflict, so the baseline 3 applies.

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?

States a specific verb and resource: 'check if an agent meets minimum trust and security requirements', with the 'B2B trust gate' framing making the domain explicit. It does not name or differentiate itself from plausible siblings like check_agent or trustgate, so it stops short of a 5.

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?

'Use this to decide whether to allow an agent to access your API or service' gives a clear decision context, but there is no when-not guidance, no prerequisites, and no named alternative for related checks. Usage is implied rather than fully specified.

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