Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Check Identity

check_identity
Read-onlyIdempotent

Check live provider identity evidence: the published ERC-8004 agent identity document and its source/status envelope, returned exactly as observed. A successful fetch shows declared identity only — it is not external certification and not settlement verification — and missing evidence stays unknown rather than being filled in. Free, read-only.

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": "check_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower; the description still adds meaningful context: the response is raw observed evidence, missing evidence remains unknown rather than being inferred, and the call is free. It does not discuss rate limits, caching, or error conditions, which keeps it below 5.

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 tight sentences, front-loaded with the action and resource before the caveats. Some phrasing is dense ('source/status envelope'), but every sentence carries distinct information with no filler.

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?

With no output schema, the description must sketch the return value, and it does so at a high level: the identity document plus its source/status envelope, passed through unmodified. It does not enumerate the document's fields or the envelope's possible status values, so an agent still lacks detail on response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4; there is nothing parameter-level the description could add. It correctly avoids restating an empty schema.

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: checks live provider identity evidence, specifically the published ERC-8004 agent identity document plus its source/status envelope. The scope wording ('returned exactly as observed') distinguishes it from verification-style siblings like verify_provider, but no sibling is named explicitly.

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?

Clear context for when to use it (retrieving declared identity evidence) and scope exclusions ('not external certification and not settlement verification'), which steer the agent away from misusing results for certification or payment confirmation. It stops short of naming the alternative tool for those cases, so routing is implied rather than explicit.

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