Skip to main content
Glama
Sign In

bitroad

by ai.bitroad
OverviewDiscussionsAdmin

Orders book

orders_book
Read-onlyIdempotent

Read one grade's book in one currency. A fungible grade: its token book, price levels { price_pence per million tokens, quantity_tokens, order_count }, bids highest first, asks lowest first. A job grade: asks as price levels { price_pence, order_count, metered_count } of the resting fixed-price listings, lowest first, and bids as the open intents' { order_count, budget_min_pence, budget_max_pence }; sealed bids are never shown. depth 1 to 50 (default 10). Aggregates only: no seller, intent or buyer. Works without credentials.

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": {
      "grade": "<grade>",
      "currency": "<currency>",
      "depth": "<depth>"
    },
    "name": "orders_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthYesPrice levels per side, 1 to 50 (default 10).
gradeYesThe grade's slug (grades_list), e.g. code_review.general or inference.large.
currencyYesThe book's currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behaviour, so the description's job is supplementary and it delivers: sort order per side (bids highest first, asks lowest first), the sealed-bid visibility rule, the no-credential requirement, and the fact that only aggregates are returned. It does not cover error behaviour for an unknown grade or what an empty book looks like, keeping it below a 5.

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

Conciseness5/5

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

Front-loaded with the core action, then the two grade variants in parallel structure, then the depth bound, then the aggregate/credential constraints. Dense with notation, but every clause carries information an agent needs; nothing is redundant 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 must carry the return-value burden and does so thoroughly for both grade types, including field names, ordering, and which data is withheld. Combined with the short parameter list and full annotation coverage, nothing material is missing for correct invocation.

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 depth and currency need no restating. The description still adds real meaning by explaining that grade selects between two structurally different books and by spelling out the unit of depth ('price levels per side'), which the schema does not convey as clearly as 'depth' alone.

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?

The opening sentence gives a specific verb and resource with explicit scope: 'Read one grade's book in one currency.' The description then distinguishes two distinct response shapes by grade type (fungible vs job), which is a level of specificity that separates it cleanly from siblings like orders_list, orders_get and intents_list_open.

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 clear usage context: aggregate depth only, 'sealed bids are never shown', and 'Works without credentials', which implicitly routes the agent away from credential-bound or per-order tools. What it lacks is an explicit when-not statement or a named alternative for retrieving individual orders or seller-level detail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bitroad toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources