Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: cancel a Zero Dark order

darkroom_cancel
Read-onlyIdempotent

An unsigned transaction to cancel an order by its commitment, from the owner or one of its session keys. It counts from the next batch (one already being proven keeps it). Simulated from the wallet.

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>",
      "commitment": "<commitment>"
    },
    "name": "darkroom_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesThe wallet's address (0x...): the transactions are built for it to sign
commitmentYesThe order's commitment, 0x + 64 hex

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 only declare the safe/idempotent/closed profile; the description adds real behavioral facts the annotations cannot express — the result is an unsigned tx the wallet must sign, authority is limited to the owner or a session key, and the cancellation takes effect from the next batch (an already-proving batch still lands). The remaining gap is what happens to escrowed collateral/funds on cancel and whether any fee is charged.

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?

Three short sentences, front-loaded with what the tool returns and who may call it, with no filler. The phrase 'It counts from the next batch' is terse to the point of being cryptic for a reader unfamiliar with batch semantics.

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 two-parameter prepare-style tool with no output schema, the description covers the meaningful surface: return type (unsigned tx), authorization, timing semantics, and that it is simulated against the wallet. Only the post-cancel state of the order's funds and the expected signing/broadcast follow-up are missing.

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%, so both parameters are already documented. The description reinforces the meaning of commitment (the order's identifier) and constrains wallet to the signing owner/session key, which is useful but adds little beyond the schema's own wording.

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?

Names a specific verb and resource ('cancel an order by its commitment') and makes clear the output is an unsigned transaction rather than an executed cancellation. The Zero Dark/darkroom scoping is only implicit in the tool name, so it never explicitly rules out the similarly named cancel_order or bailout_cancel siblings.

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 darkroom-specific cancel path and that the caller must be the owner or a session key. There is no explicit 'use this instead of cancel_order when...' routing, which matters given several cancel-shaped siblings in the namespace.

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