Skip to main content
Glama

World brief

world_brief
Read-onlyIdempotent

Macro & prediction market briefing: Polymarket and Kalshi election/macro odds, biggest 24h movers, tokenized US equities/gold, EUR/USD, and crypto news. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). 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": "world_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicsNooptional comma-separated topics, up to 5
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/5.0
Behavior4/5

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

The description supplies behavior the annotations cannot: a $0.01 per-call charge, the x402 rail and accepted assets (USDC on Arc/Base/Solana, XNT on X1), and the fact that the purchase settles inside the second call. This is exactly the kind of cost/auth disclosure an agent needs. The only residual tension is that readOnlyHint=true sits alongside an in-call fund transfer; the description discloses this openly, so an agent reading it is not misled.

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?

Two sentences, front-loaded with what the briefing contains, then the payment mechanics. The chain/token parenthetical is dense but each item is functional. Nothing is wasted, though the asset list could be tightened.

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 enumeration of covered markets stands in for a return-value description and does so adequately. Cost, rails, and the two-call handshake are all covered for what is a zero-required-parameter paid read. Minor gaps (failure/refund behavior, freshness of the odds) are not fatal.

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 the property definitions already explain `topics` and `payment`. The description additionally gives the `payment` parameter its real meaning as a signed PAYMENT-SIGNATURE payload whose submission completes the purchase, which is meaning beyond the schema's phrasing. `topics` semantics are left entirely to the schema.

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 names the resource precisely and enumerates its contents: Polymarket/Kalshi odds, 24h movers, tokenized equities/gold, EUR/USD, and crypto news. That is far more specific than the bare name 'world_brief' and is unmistakable against the arc_* payment/analytics siblings. It is a noun-phrase label rather than an explicit verb+resource, which keeps it just short of a 5.

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 an explicit operational recipe: call once without `payment` to obtain terms, sign them with your own wallet, then call again with `payment`. That removes the main ambiguity for an agent attempting a paid call. It does not say when to prefer this briefing over other data tools, but no sibling covers the same market-briefing content.

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