Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Zero Dark: a wallet's orders

darkroom_orders
Read-onlyIdempotent

A wallet's Zero Dark orders as the chain has them: commitment, market, the session key that committed it, when, filled lots and status (live, cancelled, filled, done). An order's terms are not on chain until any part of it fills, or a stale removal is tried on it (whether it succeeds or fails); then the whole opening is in that transaction. Until then the agent that placed an order keeps them.

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": {
      "wallet": "<wallet>"
    },
    "name": "darkroom_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet's address (0x...): the transactions are built for it to sign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses an important behavioral caveat: order terms are not on chain until a fill occurs or a stale removal is attempted, and until then they remain with the placing agent. It also clarifies the status values and the data visible for each order, which materially helps an agent interpret results.

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?

The description is front-loaded with the resource and returned fields, then adds the on-chain visibility caveat without redundant wording. It is dense but efficient, and each sentence contributes useful meaning.

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 low-complexity, one-parameter read tool without an output schema, the description gives enough detail about the returned fields and the important on-chain visibility limitation. It does not address pagination, ordering, or empty-result behavior, but those are minor omissions for this scope.

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

Parameters3/5

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

Schema coverage is 100% for the single wallet parameter, and the schema already explains that it is the wallet address for which transactions are built to sign. The description adds only the wallet-scoped framing, which is already implied by the tool name and schema; this meets the baseline but does not add parameter-level detail beyond 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 states a specific resource and scope: a wallet's Zero Dark orders as the chain has them, and it enumerates the returned fields including commitment, market, session key, timestamp, filled lots, and status. It is clearly more than a tautology, but it does not explicitly differentiate itself from nearby siblings such as darkroom_order, darkroom_fills, or darkroom_tape.

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?

The wallet-scoped framing implies this is the tool for listing a wallet's orders, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. The caveat about on-chain visibility is useful context, yet it does not tell an agent when to choose this tool over darkroom_fills or darkroom_order.

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

All Borro 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