Skip to main content
Glama

agent_trust_score

Read-onlyIdempotent

[READ] Composite 0..1 trust score over six optional signals (EigenTrust settlement graph, Shillbot reputation, game win rate, curator tier, credit-web position, AgentRank); weights renormalize over present signals and confidence counts them. Returns a per-signal breakdown plus signal_as_of freshness — the score is auditable, not a black box.

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

Input Schema

NameRequiredDescriptionDefault
walletNoWallet pubkey to score. Omit to query the caller's currently-registered wallet.
agent_rankNoOptional Hyperspace AgentRank score in 0..1. Pass when available; the composite formula folds it in. AgentRank integration is queued; for now callers compute it externally.
curator_tierNoOptional curator-tier ascription (`"first-party"`, `"vetted"`, `"discovered"`) — pass when you've already looked the agent up in the Layer 3 directory and want to fold the tier into the composite. Omit to skip the curator signal.
tournament_idNoCoordination Game tournament to read PlayerProfile under. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: the composite is auditable (returns a per-signal breakdown), weights renormalize over present signals, and `confidence` counts them. It also discloses freshness via `signal_as_of`. This is meaningful added context, though it doesn't detail failure modes or edge cases like missing wallet.

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?

A single dense sentence that front-loads the core purpose ('Composite 0..1 trust score'), then packs the signal list, renormalization behavior, and return shape without waste. Every clause earns its place; no filler or repetition.

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, idempotent tool with 100% schema coverage and no output schema, the description is nearly complete. It explains the return shape (breakdown, signal_as_of) and the scoring behavior. The only minor gap is that it doesn't state what happens when no signals are present or how to interpret the confidence value, but these are edge details an agent can infer from the schema and annotations.

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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description adds the composite formula context (weights renormalize, confidence counts signals) but doesn't add per-parameter meaning beyond the schema. Baseline 3 is appropriate since the schema carries the heavy lifting.

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?

The description states a specific verb ('Returns'), a precise resource (composite 0..1 trust score), and enumerates the six optional signals that feed it. It also distinguishes itself from a black-box by promising an auditable breakdown, which separates it from sibling tools like agent_reputation_leaderboard or query_agent_credit_web_score.

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?

The description implies when to use it: when an auditable composite trust score over multiple signals is needed, and notes that weights renormalize over present signals. It doesn't explicitly name alternatives or exclusions, but the '[READ]' prefix and the signal list make the context clear. Sibling tools like query_agent_credit_web_score are implicitly alternatives for single-signal queries, though not named.

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