Skip to main content
Glama

Market pulse

market_pulse
Read-onlyIdempotent

One Base read of the market pulse: a score from 0 to 100, risk-on or risk-off, five reasons, and the sources that answered. Public data only. Not financial advice. $0.005 per call over x402 (USDC on Base only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_pulse"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: public data only, not financial advice, price ($0.005/call), accepted rail (x402/USDC on Base only), and the fact that settlement happens inside the call. The annotations already declare read-only/non-destructive/open-world, so these pricing and payment-handshake disclosures are the real value-add. A note on whether the paid call counts as a ledger mutation, given readOnlyHint=true, would close the remaining gap.

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 read and its outputs, then the pricing and payment mechanics; every clause carries information (price, rail, currency, protocol). The style is dense and telegraphic ('One Base read'), and the final sentence packs three steps into one line, but nothing is filler.

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

Completeness5/5

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

There is no output schema, so the description compensates by enumerating the returned fields, and it fully covers the one optional parameter's payment flow, cost, and currency. Nothing an agent needs to invoke this correctly is missing.

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?

Schema coverage is 100% and the schema already describes `payment` as the base64 PAYMENT-SIGNATURE payload, so the baseline is 3. The description goes further by explaining the sequence in which `payment` should be omitted versus supplied, which the schema does not convey.

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

Purpose5/5

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

States a specific verb and resource ('One Base read of the market pulse') and enumerates exactly what comes back: a 0-100 score, risk-on/risk-off, five reasons, and the answering sources. This is far more specific than the title alone and lets an agent know the payload shape without any schema.

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?

Gives a precise two-call protocol: call without `payment` to get terms, sign with your own wallet, then call again with `payment`. That is explicit invocation guidance. It does not say when to prefer this over the similarly named market siblings, but per the rules that miss is not inferred from names alone, so 4 rather than 5.

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