Skip to main content
Glama

protocol_changes

Everything that changed in one protocol over a window: Snapshot proposals with live vote tallies, quorum and end time; proxy upgrades and admin changes with transactions; and the current implementation and admin of each watched contract. Costs $0.005 (x402, USDC).

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": {
      "protocol": "<protocol>"
    },
    "name": "protocol_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days (default 30, max 90)
protocolYesProtocol id from /v1/protocols, e.g. aave, uniswap, lido, usdc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a concrete behavioral trait: a $0.005 x402/USDC cost, which is important context an agent cannot get from structured fields. However it says nothing about rate limits, error behavior, response size, or the fact that payment must be settled before the call, leaving meaningful gaps for a paid endpoint.

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 dense sentence, front-loaded with the purpose and followed by the content breakdown, with the cost placed last where it does not obstruct scanning. The semicolon-delimited list is efficient, though the enumerated clauses run together without further structure.

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, so the description properly explains what is returned, and it adds the payment requirement – together covering the two things an agent most needs for this call. Minor gaps remain around result volume and what happens when a protocol has no changes in the window.

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%, with 'protocol' documented as an id from /v1/protocols and 'days' bounded 1-90 with a default of 30, so the schema does the heavy lifting. The description adds only loose framing ('one protocol', 'over a window') and no format or enum hints beyond the schema, 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 specific verb+resource ('Everything that changed in one protocol over a window') and enumerates the return contents (Snapshot proposals with tallies/quorum/end time, proxy upgrades, admin changes, current implementation and admin). It does not explicitly contrast itself with the sibling protocol_digest, so an agent must infer the distinction, keeping it below a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named despite protocol_digest and quick_check being plausible substitutes. The 'over a window' phrasing implies a look-back use case but never states the condition that should select this tool.

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