BlindOracle

execute_arbitrage_trade

Automate cross-market arbitrage trade execution by specifying opportunity details, trade size, profit threshold, and enabling dry run for risk-free testing.

Instructions

Execute cross-market arbitrage trade @requirement: REQ-ARB-001 - Cross-market arbitrage Properties: Autonomy(+0.6), Self-Organization(+0.4)

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": {
      "opportunity": "<opportunity>"
    },
    "name": "execute_arbitrage_trade"
  }
}

Input Schema

Name	Required	Description	Default
`dry_run`	No
`max_size`	No
`opportunity`	Yes
`min_profit_threshold`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, and the description only includes cryptic metadata about autonomy and self-organization. It does not disclose whether the trade actually modifies state, requires permissions, or has side effects. The behavioral impact is unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but includes extraneous content like '@requirement: REQ-ARB-001' and property values that do not clarify usage. It is not optimally structured and wastes space on non-functional metadata.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of an arbitrage trade with multiple parameters and an output schema, the description omits critical information such as return values, risk implications, and invocation constraints. It is insufficient for correct tool use.

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

Parameters1/5

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

The input schema has 0% description coverage, and the tool description does not explain any parameters (e.g., 'opportunity', 'dry_run', 'max_size', 'min_profit_threshold'). The agent gains no understanding of how to populate 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 clearly states 'Execute cross-market arbitrage trade' which is a specific verb+resource combination. However, it does not distinguish from the sibling tool 'submit_arbitrage_job', leaving ambiguity about when to use this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'submit_arbitrage_job' or 'get_trading_signals'. The description lacks context on prerequisites or appropriate scenarios.

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