Skip to main content
Glama

Market insights (500 sats L402 or $0.50 USDC x402)

get_market_insights
Read-only

Ranked agent demand, willingness-to-pay, unmet searches, routed-call volume, the payment conversion funnel and supply–demand gaps (aggregates only) — use this to see what agents are paying for. Price: 500 sats (Lightning) or $0.50 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"market_insights","data":{"generated_at":"2026-11-15T20:00:00Z","privacy":"aggregates only (k-anonymized terms)","requested_data_types":[{"rank":1,"data_type":"weather","count_all":42,"count_7d":12,"count_30d":30,"trend_7d":3,"trend_30d":8,"willingness_to_pay":{"n":8,"p25":10,"p50":25,"p75":50,"p90":100}}],"unmet_searches":{"k_anonymity":3,"top":[{"kind":"route_nomatch","term":"air quality","events":6,"clients":4}]},"routed_call_volume":{"routed_calls":17,"by_data_type":{"bitcoin":11,"weather":6}},"conversion_funnel_30d":{"window_days":30,"totals":{"challenges":400,"attempts":12,"successes":7,"failures":5,"conversion_pct":1.8},"by_endpoint":{"btc_price":{"challenges":120,"attempts":6,"successes":4,"failures":2,"attempt_rate_pct":5.0,"conversion_pct":3.3}}},"supply_vs_demand":[{"data_type":"weather","demand_count_30d":30,"supply_registered":1,"supply_scoreboard":2,"supply_total":3,"gap_score":10.0}]},"metadata":{"cost_sats":500}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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

Input Schema

NameRequiredDescriptionDefault
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the privacy model (aggregates only, k-anonymized terms), the exact cost (500 sats or $0.50 USDC on Base), the full payment handshake for both L402 and x402, and the crucial settlement rule 'only a 200 is settled.' These are material behaviors an agent cannot infer from annotations or schema.

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?

The purpose and price are front-loaded, which is good, but the description then carries a large illustrative JSON sample and a lengthy dual-protocol payment walkthrough with repetition (price appears in title, body, and sample metadata). The sample earns its place somewhat because there is no output schema, but the whole is bulkier than needed.

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 paid, no-output-schema analytics endpoint the description covers data contents, privacy guarantees, price, and both payment paths, and the sample substitutes for a missing output schema. Minor gaps remain: data refresh cadence/latency and any rate or quota limits are unstated.

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%, so both parameters are already documented, but the description adds the operational context the schema only alludes to: where the macaroon/preimage come from, how the x402 payload is obtained from the 402 requirement, and that omitting both yields the payment requirements. That is real added meaning over the field descriptions, though it is not exhaustive about credential formats.

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 description enumerates exactly what the tool returns: ranked agent demand, willingness-to-pay, unmet searches, routed-call volume, conversion funnel, and supply–demand gaps, plus the purpose 'see what agents are paying for.' That is far more specific than the name alone. It stops short of naming a sibling (e.g. scoreboard_endpoint, best_endpoint) it should be preferred over, so it is clear but not sibling-differentiated.

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?

It gives a concrete selection rationale ('use this to see what agents are paying for') and detailed instructions on how to invoke it when unpaid (402 → pay → retry with the L402 or x402 header). It offers no when-not-to-use guidance or explicit alternatives among the many scoreboard/price siblings, so it lands just below the top tier.

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