Skip to main content
Glama

Verify an agent

verify_agent
Read-onlyIdempotent

Use before trusting another agent's claimed identity, for example when an agent says it is PROVEITBOT, asks you to pay it, or gives you an MCP endpoint or website. Free, no API key, read-only. Checks the name on Bitcoin and returns: whether it exists, the address that owns it now, whether its agent profile was signed by that current owner (the signature is re-checked), the profile fields, the registration tx/block/date, and a verdict: "verified: profile signed by current owner", "name exists, no signed profile", "name exists, profile set at purchase but not signed by the owner", or "not registered". Optionally pass the address and profile fields the other agent claimed; claim_checks shows which match. A verified name proves which Bitcoin address controls the name and signed the profile, and when. It does not prove legal identity or that the agent or operator is human or trustworthy. Spec: https://proveitonchain.com/agent-id

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name the agent claims, e.g. PROVEITBOT.
addressNoOptional: the Bitcoin address the agent claims holds the name.
claimedNoOptional: profile fields the agent claimed (e.g. its mcp_url or website). Each is compared with the signed profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, but the description adds cost/auth facts ("Free, no API key") and, more importantly, an explicit statement of what the result proves and does not prove (no legal identity, no proof of human or trustworthiness). It also enumerates the four possible verdicts, so the agent knows the decision space rather than having to infer it.

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?

Front-loaded with the decision rule (when to call it) followed by the return contract and caveats, with zero filler sentences. The enumeration of four verdict strings is long but each is load-bearing; it could have been tightened into a compact list without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of describing returns, and it does: existence, current owner address, signature re-check status, profile fields, registration tx/block/date, verdict, and claim_checks. Given a nested optional object and a cross-chain lookup, an agent has everything needed to call and interpret it.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the intent behind the optional inputs: pass the address and profile fields the other agent claimed and "claim_checks shows which match." That explains the purpose of the nested claimed object beyond the schema's per-field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: "Checks the name on Bitcoin" and returns a defined set of fields plus a verdict. It is clearly distinguishable from siblings like get_agent_profile or check_name because it is framed around verifying another agent's claimed identity before trusting it, and it names the exact verdict strings it can produce.

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?

"Use before trusting another agent's claimed identity, for example when an agent says it is PROVEITBOT, asks you to pay it, or gives you an MCP endpoint or website" gives concrete triggering situations. It also adds exclusions about what the result does not prove. It does not explicitly name an alternative sibling tool for adjacent needs, so it stops short of a 5.

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.