Skip to main content
Glama

Market brief: trade this market or not

pm_market_brief
Read-only

The full report: exact fill and slippage for your size, total cost including fees and builder fee, the breakeven probability you need to believe, reward eligibility and payout estimate, net edge against your own probability estimate, and a verdict (operate / operate_partial / do_not_operate / insufficient_data) with the reasons enumerated. Send your book and the market config; nothing is stored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>",
      "size_shares": "<size_shares>"
    },
    "name": "pm_market_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoOrder book: bids and asks with price and size in shares
roleNo
sideNo
rewardsNo
categoryYesMarket category, sets the fee rate
questionNo
market_idNo
price_hintNo
builder_bpsNo
queue_aheadNo
size_sharesYesOrder size in shares
your_probabilityNoYour own probability estimate. Without it the report returns the breakeven and no verdict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'nothing is stored', which is meaningful context about side effects. It also discloses the verdict vocabulary (operate / operate_partial / do_not_operate / insufficient_data) and that reasons are enumerated, so the agent knows the shape of the decision output. Missing: any statement about determinism, latency, or error behavior for malformed books.

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?

Effectively one long enumerative sentence followed by a short input-requirement sentence. The list is dense but every clause names a distinct output, and the 'full report' framing is front-loaded. Slightly overpacked for a single sentence, but no filler.

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?

With 12 parameters, nested objects, and no output schema, the description carries a heavy load. It compensates well on the return side by enumerating the report's contents. It leaves gaps on the input side: role, side, price_hint, queue_ahead, and the rewards sub-fields are never explained, and the required set (category, size_shares) is not signposted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given schema coverage of 33% across 12 parameters with nested objects, the description does substantial compensatory work. It maps 'your size' to size_shares, 'the market config' to category/market_id, explains builder_bps in terms of the builder fee it produces, and calls out that your_probability drives net edge and that omitting it degrades the report to breakeven-only with no verdict.

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 opens with a specific framing ('The full report') and enumerates the concrete outputs: exact fill and slippage, total cost including fees and builder fee, breakeven probability, reward eligibility/payout, net edge, and a named verdict enum. That is a real verb+resource statement an agent can act on. It does not explicitly contrast itself with the sibling tools (pm_order_book_fill, pm_platform_fee, pm_reward_eligibility), which is why it falls short of 5.

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?

Usage is implied rather than stated: an agent can infer this is the aggregate report you call when you want the whole picture rather than a single metric. 'Send your book and the market config; nothing is stored' gives the input expectation and a privacy note. There is no explicit when-to-use/when-not guidance and no pointer to the narrower sibling tools for cheaper partial queries.

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