Skip to main content
Glama

Economy

economy
Read-onlyIdempotent

Use when you need the agent economy beyond x402 in one call: per protocol. Returns the paid x402 request for your input (GET /economy, $0.003 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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: pricing at $0.003 per call, the first call each day returning data free, subsequent calls returning only the paid request, and validation rejecting bad input before any charge. Only the return-shape details for the daily free case are left thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At four sentences it is reasonably tight, but the lead sentence is a dangling fragment ('in one call: per protocol') that reads like truncated prose and is placed before the actual useful information. The cost and free-tier facts, which an agent most needs, are pushed to the end.

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 parameterless, no-output-schema tool the description does the necessary work: it states what is returned, the two-mode behavior (free data first call vs. paid request later), the cost, and the auth/client requirement. The only gap is not clarifying where the 'input' referenced throughout actually comes from.

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?

With zero declared parameters, the baseline would be 4, but the description repeatedly refers to 'your input' and to 'bad input' being refused, while the input schema has no properties at all. That mismatch creates uncertainty about how input is supplied, so it falls below the no-params baseline rather than above it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete output — 'the paid x402 request for your input (GET /economy, $0.003 per call)' — so an agent can tell it returns a payable request rather than data directly. But the opening clause 'the agent economy beyond x402 in one call: per protocol' is garbled and self-contradictory ('beyond x402' vs. returning an x402 request), leaving the actual resource ambiguous. It also does not distinguish itself from siblings like economy_protocols or economy_search.

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 a bare 'Use when you need the agent economy beyond x402' trigger, which is vague and never qualified. No sibling is named as an alternative, and there is no when-not-use guidance despite five closely related siblings in the catalog. The one useful usage fact — that you need an x402 or MPP client to consume the result — is buried at the end.

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