Skip to main content
Glama
Sign In

Borro

by markets.borro
OverviewDiscussionsAdmin

A trade account's triggers

trigger_list
Read-onlyIdempotent

The live triggers on a trade account (account, or the wallet's own): each with its condition in words, the stock's price now and how far it is from firing (in dollars and percent; a guard's LTV now and about where the price takes it to its LTV), whether it holds now (the account's own check) and why not, who set it, its slip, tip and expiry, and the fire transaction anyone may send once it holds. Triggers do not fire while the stock market is shut or the feed has not printed within 25 hours; a price crossed while it is shut (a weekend, a holiday) fires once the market opens again, at the price the feed prints then, within the trigger's slip, and after a gap that price can be well past the trigger's.

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

Input Schema

NameRequiredDescriptionDefault
walletNoThe account's owner (when account is not given)
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
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds substantial domain context: what each trigger reports, how 'holds now' and 'why not' are evaluated, and crucially the firing rules during market closure and stale feeds. This goes well beyond the safety profile and helps an agent interpret the output correctly.

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 return content, and most clauses carry substantive information needed to interpret trigger status. The first sentence is a dense run-on with many parentheticals, which slightly hurts readability, but the content largely earns its place.

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 explain the return shape—and it does so thoroughly, covering conditions, price distance, LTV, hold status, setter, slip/tip/expiry, and fire transaction. Combined with complete parameter coverage and read-only annotations, the description gives an agent everything needed to invoke and interpret the tool.

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%, with both wallet and account documented directly in the schema. The description repeats the account-or-wallet relationship but does not add syntax, formatting, or other semantics beyond what the schema already provides, so the baseline 3 is appropriate.

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 clearly identifies the resource as live triggers on a trade account or the wallet's own account, and enumerates the returned fields. An agent can infer this is a read/list operation, but there is no explicit verb and no direct distinction from siblings such as trigger_set, trigger_cancel, or trigger_fire.

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: an agent would use this to inspect live triggers and their status. However, the description never states when to use this versus trigger_set, trigger_cancel, or trigger_fire, and gives no explicit 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