Skip to main content
Glama

Turingate

Verify an AI agent

verify_agent
Read-only

Check what an AI agent presented: a Turingate pass token and/or a Web Bot Auth signed request (Signature, Signature-Input, Signature-Agent headers). Returns one decision with the agent, its operator, the verified owner, scopes and spending limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo
tokenNoTuringate pass token
amountNo
requestNo{ method, url, headers } of a Web Bot Auth signed request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the behavioral shape of the call: it accepts a token and/or a signed request (consistent with zero required params) and returns exactly one decision containing agent, operator, verified owner, scopes and spending limit. Since there is no output schema, that return-value disclosure is genuinely useful. It stops short of saying what a negative decision looks like or what happens when neither input is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded with the essential information: what is checked first, what comes back second. The parenthetical header list is dense but earns its place by disambiguating the nested request object.

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 read-only verification tool with no output schema and a nested-object parameter, the description does the important work: it enumerates the return fields and the accepted credential forms. The remaining gap is the semantics of scope/amount and the possible decision outcomes, which an agent would need in order to call this with confidence.

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 coverage is 50%, and the description clarifies the signed-request object by naming the three Web Bot Auth headers, which the schema only summarizes as '{ method, url, headers }'. However, 'scope' and 'amount' are never explained — it is unclear whether they are the requested scope and spend to authorize, which is exactly the ambiguity that matters for a verification call.

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 names a specific verb and resource ('Check what an AI agent presented') and enumerates the two accepted credential types plus the returned decision fields, so the tool's job is unambiguous. It does not explicitly distinguish itself from the sibling check_agent_readiness, which is the only thing keeping it from 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no reference to the alternatives (check_agent_readiness, get_challenge, submit_answers) that an agent might otherwise pick. The verification context is implied by the credential list, but the agent must infer the routing decision on its own.

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.