Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

Prepare: cancel a trigger

trigger_cancel
Read-onlyIdempotent

Unsigned transaction cancelling a live trigger on the trade account: the owner cancels any, the agent the ones it set. 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>",
      "id": "<id>"
    },
    "name": "trigger_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe trigger's number (trigger_list shows it)
walletYesThe wallet's address (0x...); the transactions are built for it to sign
accountNoA trade account's address (default: the wallet's own, as its owner; an agent gives its owner's account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the real value added is the disclosure that this only builds an unsigned transaction for the wallet to sign and that it is simulated from the wallet, plus the owner-vs-agent authority rule. It stops short of saying what the caller must do with the unsigned transaction or what the simulation returns.

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?

A single dense sentence with the core operation front-loaded and no filler. Every clause (unsigned, live, ownership rule, simulated) carries information.

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?

With no output schema, the description should hint at what comes back; 'unsigned transaction ... simulated from the wallet' implies a prepared, simulated transaction but not its shape. For a three-parameter preparation tool that is nearly complete.

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 all three parameters are already documented. The description adds only indirect color on `account` via the owner/agent wording; it gives no extra detail on `id` lookup or wallet formatting beyond the schema.

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?

States a specific verb and resource (cancel a trigger), the scope (live triggers on the trade account), and the authorization split (owner cancels any, agent only the ones it set). That distinguishes it cleanly from trigger_set, trigger_list and trigger_fire without needing their schemas.

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 permission model and the 'live trigger' qualifier imply when the call is valid, but the description never names alternatives (trigger_set, trigger_fire) or states exclusions such as what to do with already-fired triggers. Usage is inferable rather than spelled out.

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