Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

trust_agent_attestation

Check an agent's operator verification and observed on-rail payment history to support pre-payment trust decisions. Returns read-only advisory signals for a wallet or identifier, not a guarantee.

Instructions

Attestation signals for an agent: operator verification status plus observed on-rail payment history for the given wallet or identifier. Read-only and advisory — signals only, never a guarantee of trustworthiness. For domains use trust_verify_status; for a pre-payment decision use trust_screen. Paid: $0.02 USDC on Base per attestation — the rail quotes each call via 402; this server verifies the quote (exact scheme, Base network, USDC, Steward payee) and settles from your wallet automatically, refusing quotes over your per-call or daily spend caps. Your payer key never leaves your machine.

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": {
      "agent": "<agent>"
    },
    "name": "trust_agent_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesAgent identifier: EVM address, Solana address, or a 1-128 char id.
operator_domainNoOptional operator domain to cross-check against Steward Verified status (e.g. example.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses read-only/advisory semantics, an explicit non-guarantee caveat, the price ($0.02 USDC on Base), the 402 quote flow, the exact validation criteria the server enforces (scheme, network, USDC, Steward payee), automatic settlement, spend-cap refusal behavior, and that the payer key stays local. This is far beyond what a name or schema conveys.

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?

Purpose and the sibling routing are front-loaded, which is the right ordering for a selection decision. The payment-mechanics sentence is long, but every clause (quote validation, caps, key custody) is material given the absence of annotations, so it earns its space despite the density.

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?

No output schema exists, and the description sketches return content well by naming the two signal classes (verification status, on-rail payment history). What is thinner is the shape of a returned attestation (fields, confidence, staleness), which an agent would have to discover empirically. For a 2-param read tool with full schema coverage, this is nearly complete.

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 both `agent` and `operator_domain` are already documented with formats and length bounds. The description restates the identifier concept ('given wallet or identifier') but adds no syntax or cross-check detail beyond the schema. Baseline 3 is appropriate when the schema does 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?

States a specific resource ('attestation signals for an agent') and enumerates the signal types: operator verification status plus observed on-rail payment history. It explicitly names the siblings it is not (trust_verify_status for domains, trust_screen for pre-payment), so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing conditions: 'For domains use trust_verify_status; for a pre-payment decision use trust_screen.' It also frames the tool's role as advisory/read-only signals rather than a decision, which further scopes when to reach for it. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools