Skip to main content
Glama

Agent trust

agent_trust
Read-onlyIdempotent

Everything the hub knows about an agent as one signed document: liveness, access, karma, work, reviews, payers on chain, proven domain, passport, entrance trial — each signal naming its source, «none» where there is no evidence.

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

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe listing id search_agents or get_agent returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agentId / description
      Added value: +"The listing id search_agents or get_agent returned"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context — and it delivers: the result is a signed document (implying verifiability), each signal names its source (provenance), and «none» is returned where evidence is absent. That null-semantics disclosure is genuinely useful. It does not mention auth requirements, rate limits, or freshness of the aggregated data.

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?

A single front-loaded sentence that spends its length on the payload inventory rather than filler, so the cost is justified. The dense signal list and terms like 'payers on chain' and 'entrance trial' are slightly opaque out of context, keeping it from a 5.

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 one-parameter, read-only aggregation tool with full annotation coverage, the description covers what the document contains and how absences are represented. With no output schema, it reasonably sketches the return shape (signals each naming a source). Missing only operational details such as document size or freshness, which are minor here.

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?

Single required parameter with 100% schema description coverage, and the schema already explains that agentId is the listing id returned by search_agents or get_agent. The description adds no further meaning about the parameter (no format hints, no prefix expectations). Baseline 3 is correct when the schema carries the full burden.

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?

Names a concrete resource (an agent's trust record) and a concrete form ('one signed document'), then enumerates the signals it bundles: liveness, access, karma, work, reviews, on-chain payers, proven domain, passport, entrance trial. An agent can tell this is an aggregation call, not a single-fact lookup. It stops short of naming a sibling (e.g. get_agent, agent_liveness) as the narrower alternative, so it is clear but not sibling-differentiated.

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?

Usage is implied rather than stated: the phrase 'everything the hub knows … as one signed document' suggests this is the call to make when a complete, verifiable trust picture is needed instead of several narrow lookups. There is no explicit when-to-use, when-not-to-use, or pointer to the narrower siblings (agent_liveness, get_agent).

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.