Skip to main content
Glama

protocol_digest

One call across every watched protocol: governance votes open now, proposals decided in the window with the winning choice, and every contract upgrade or admin change. Costs $0.02 (x402, USDC).

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 7, max 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral load, and it does contribute a key operational fact: the call costs $0.02 via x402 in USDC, which signals a payment flow an agent must handle. It does not disclose read-only semantics, whether payment is per-call or per-session, latency, pagination, or result size, leaving meaningful gaps.

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?

Two tight sentences with no filler: the content scope is front-loaded and the cost/payment detail follows as a discrete operational note. Every clause conveys distinct information an agent needs.

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-optional-parameter read aggregate with no output schema, the description covers what categories of data come back well enough to decide and invoke. The main remaining gap is the response shape and behavior on empty windows, plus the mechanics of the x402 payment flow.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'days' including the default of 7 and max of 30. The description's phrase 'in the window' only loosely ties to that parameter and adds no format or edge-case meaning, so baseline 3 applies.

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?

The description names a concrete resource set ('every watched protocol') and enumerates exactly what is returned: open governance votes, decided proposals with the winning choice, and contract upgrades/admin changes. Scope ('one call across every watched protocol') implicitly contrasts with per-protocol siblings such as contract_check and protocol_changes, though no sibling is named explicitly.

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 only implied: an agent can infer this is the cross-protocol aggregate versus narrower per-protocol siblings, and the window parameter implies recurring digest use. There is no explicit statement of when to prefer this over protocol_changes, contract_check, or quick_check, and no exclusion or prerequisite guidance beyond the price.

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