Skip to main content
Glama

list_protocols

Every covered protocol: id, name, Snapshot spaces and watched contracts on Ethereum and Base. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With zero annotations the description carries the full burden; it discloses the response payload contents and adds 'Free', hinting at no cost/auth barrier. It says nothing about pagination, completeness guarantees, or rate limits, so transparency is partial but the operation is a low-risk read.

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 with no filler and the returned fields listed up front. It is slightly telegraphic—no verb and a colon-fragment style that reads more like a data label than a tool description.

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 zero-parameter list tool with no output schema, the description supplies the essential return shape (id, name, Snapshot spaces, watched contracts across Ethereum and Base). Only the absence of any usage framing or scope caveats keeps it from being complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The field list it does provide describes output, not inputs.

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 the resource ('Every covered protocol') and enumerates the returned fields (id, name, Snapshot spaces, watched contracts on Ethereum and Base), so an agent knows exactly what it gets. The verb is only implied by 'Every covered protocol' and nothing distinguishes it from siblings like protocol_digest or protocol_changes.

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?

No when-to-use statement and no reference to alternatives, despite four siblings that plausibly overlap (protocol_digest, protocol_changes, quick_check). The breadth implied by 'Every covered protocol' weakly suggests a discovery/enumeration role, but the agent must infer that itself.

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