Skip to main content
Glama

Machine money: headline figures

market_state
Read-onlyIdempotent

Use this for today's headline figures. The ledger's headline figures for AI-agent money, each with its value, unit, measurement time and definition id. On Base: money agents paid to others after registration (counted), daily spending by the day it was paid (last day, 7-day and 30-day averages), the part that went into positions they still hold, what left their control, the routing hops and pre-registration history excluded, how many agents are ranked (L7+ paid someone, L8 funded, L9 repeat counterparties), agent income, x402 seller inflow, treasuries, concentration, detections and the address-poisoning watch. On other chains: ERC-8004 registrations on seven chains, what registration owners paid on BNB Smart Chain, Ethereum, Arbitrum, OP Mainnet and Polygon, and Solana agent registrations and payments.

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

Input Schema

NameRequiredDescriptionDefault
compactNoLeave out the reading notes and the previous-sample block (figures, data quality and licence stay)

Output Schema

NameRequiredDescriptionDefault
as_ofYes
chainNo
sinceNo
sourceNo
figuresYes
readingNo
data_qualityNo
days_still_scanningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "description": "Leave out the reading notes and the previous-sample block (figures, data quality and licence stay)",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "chain": {
      +      "type": "string"
      +    },
      +    "data_quality": {
      +      "type": "object"
      +    },
      +    "days_still_scanning": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "figures": {
      +      "additionalProperties": {
      +        "properties": {
      +          "as_of": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "definition_id": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "stale": {
      +            "type": "boolean"
      +          },
      +          "unit": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "value": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "value"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "object"
      +    },
      +    "reading": {
      +      "type": "string"
      +    },
      +    "since": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "figures"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine domain context about counting methodology and exclusions ('money agents paid to others after registration', 'routing hops and pre-registration history excluded'), but says nothing about freshness, caching or response shape beyond what the output schema provides.

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

Conciseness2/5

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

The first sentence is well front-loaded, but the second is one enormous run-on enumerating dozens of metrics across chains. Much of that enumeration duplicates the output schema, and the sheer density makes it hard for a reader to extract the operative points.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the exhaustive metric listing is largely redundant, while genuinely useful context is missing: how this differs from metric_history or since_last, and whether the snapshot is per-chain or global. For a multi-chain headline tool with many siblings, that leaves real gaps.

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 optional parameter with full schema coverage whose description already explains compact ('Leave out the reading notes and the previous-sample block'). The tool description never mentions compact, so it adds no meaning 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?

The opening line states a concrete resource ('today's headline figures') and the second sentence clarifies it is the ledger's AI-agent money figures with value, unit, measurement time and definition id. That is specific enough to know what comes back, but nothing distinguishes it from siblings like list_metrics, metric_history or since_last, which plausibly return overlapping metric data.

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?

'Use this for today's headline figures' implies a snapshot/current-state use case, but no explicit when-not conditions or named alternatives are given. An agent facing 25 siblings has to infer that metric_history is for time series and since_last for deltas.

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.