Skip to main content
Glama

Check trust

check_trust
Read-only

Look up a bot's full public trust profile (use check_payment instead when you are about to pay a wallet): trust_level (unknown/caution/fair/good/excellent), score (for a registry bot, 0-100: how strong its public record is, with the parts it is made of under rating), the reasons, and its proven identities. Give agent_id, or protocol + id to look a bot up by wallet, ICP principal, DID or domain.

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_trust"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe identity for that protocol.
agent_idNoThe bot's Keptvow id.
protocolNoOr: icp, eth, erc8004, did, web_bot_auth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, non-open-world behavior, so the bar is lower; the description adds that this is a public trust profile and defines the semantics of the returned score (0-100 for registry bots, decomposed under 'rating') along with enum-like trust_level values. It does not cover lookup-miss behavior or how a partially-proven identity is reported, which keeps it from a 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?

One dense sentence plus a second addressing sentence; the core purpose is front-loaded and nothing is redundant. The nested parentheticals make it slightly harder to scan than ideal, but every clause carries information.

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 and a low-complexity read tool, the description carries the return-value burden and does so by naming the profile fields. The remaining gap is edge-case behavior — what comes back for an unregistered or ambiguous identifier — which the schema cannot answer either.

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 100%, so 3 is the baseline, and most of the addressing detail is already in the schema. The description does add real value by explaining the either/or contract (agent_id, or protocol + id) and clarifying that the protocol-specific id may be a wallet, ICP principal, DID, or domain, which goes beyond the schema's terse enum list.

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?

"Look up a bot's full public trust profile" gives a specific verb and resource, then enumerates what the profile contains (trust_level, score, reasons, proven identities). It also names the sibling check_payment and the condition that selects it, so an agent can distinguish the two without opening either schema.

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?

Explicitly routes the payment case to check_payment ("use check_payment instead when you are about to pay a wallet") and explains how to address the target (agent_id alone, or protocol + id). It stops short of stating when-not to use this tool beyond the payment exclusion, but the alternative routing is concrete.

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