Skip to main content
Glama

Economy protocols

economy_protocols
Read-onlyIdempotent

Use when you need one agent-economy protocol in detail: every normalised row (per chain or rail, all-time and 30-day windows) for x402, Tempo MPP, Virtuals ACP, Olas, Masumi, ERC-8004. Returns the paid x402 request for your input (GET /economy/protocols, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.

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

Input Schema

NameRequiredDescriptionDefault
protocolNooptional: x402, tempo-mpp, virtuals-acp, olas, masumi, erc-8004, solana-agent-registries, base-agentic or mcp; omitted = all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations: discloses the price ($0.002 per call), the endpoint (GET /economy/protocols), that bad input is refused before any charge, that the first call each day returns data free, and that later calls return a paid request rather than the data. That last point is a critical behavioral quirk the annotations do not convey.

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?

Front-loads the use case, then pricing and payment mechanics; nearly every clause carries information. The sentence combining 'Returns the paid x402 request ... (GET ..., $0.002 per call; schema linked)' is dense and parenthetical-heavy, costing a little readability.

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?

With no output schema, the description still characterizes the return shape (normalised rows, per-chain, all-time and 30-day windows) and the two operational modes (free data vs. paid request). It leaves the exact delivery mechanism of the paid request slightly ambiguous, but an agent has enough to call and interpret results.

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 coverage is 100% and the single optional parameter already enumerates the accepted protocol slugs. The description reinforces the concept ('per chain or rail', omitted = all implied by 'one protocol') but its protocol list is a subset of the schema's values, and it adds no format or matching details beyond the schema. 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?

States a concrete outcome: 'every normalised row (per chain or rail, all-time and 30-day windows)' for a named protocol. The 'in detail' phrasing implicitly distinguishes it from the broader sibling 'economy', but no sibling is named explicitly. An agent knows what it retrieves, though 'returns the paid x402 request' muddies whether the tool delivers data or a payment instruction.

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?

'Use when you need one agent-economy protocol in detail' gives a clear selection context, and the free-first-call-then-paid-request rule tells the agent when to expect a usable payload versus a payment handoff. It stops short of naming the alternative broad tool ('economy') or stating when not to use it.

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