Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Zero Dark: the delayed tape and weekly stats

darkroom_tape
Read-onlyIdempotent

Zero Dark's venue tape, 15 minutes behind, with sizes in buckets and no accounts, and weekly per-market volume two weeks after each week. Exact fills are on chain at settlement.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavior beyond that: a 15-minute delay, bucketized sizes, omission of account identities, weekly volume published two weeks after each week, and exact fills available only on chain at settlement.

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 a single dense sentence that front-loads the resource and its key limitations. Every clause carries information about latency, aggregation, privacy, or reporting cadence. It is slightly awkward in phrasing but not padded.

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?

For a zero-parameter data tool with no output schema, the description covers the main behavioral constraints well. However, it does not describe what the tape contains beyond sizes, what dimensions or identifiers are returned, or what time range is available. An agent knows the data is delayed and bucketed but not the shape of the response.

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?

The tool takes no parameters, so there is no parameter semantics to document and the baseline is 4. The description does not need to compensate for schema gaps; the empty schema is complete on its own.

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 identifies a specific resource: Zero Dark's delayed venue tape plus weekly per-market volume. It explains distinguishing properties (15-minute delay, bucketed sizes, no account data, two-week reporting lag) and implicitly contrasts with exact on-chain fills. The term 'tape' is jargon and no verb is stated, but the scope is clear enough for an agent familiar with the domain.

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: the tool is for delayed, aggregated market data, and the closing sentence points to on-chain settlement for exact fills. There is no explicit 'use this when' instruction, no named alternative such as darkroom_fills, and no exclusions or prerequisites.

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