Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

list_backtest_markets

Read-onlyIdempotent

List available execution venue and quote-token choices for a backtest. Use when the user asks for alternatives. Missing market details are selected automatically in backend ranking order, retaining supplied dimensions. Do not ask for a market choice unless the user requests one. Availability here does not guarantee historical coverage; submission checks the chosen window.

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": {
      "asset": "<asset>"
    },
    "name": "list_backtest_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset symbol, e.g. BTC or ETH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds genuinely non-obvious context: defaults are filled in by backend ranking order while supplied dimensions are retained, and availability does not imply historical coverage because the submitted window is checked. It stops short of saying what fields come back or whether the list is paginated.

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?

Four short sentences, front-loaded with the purpose and then the constraints; little waste. The clause 'retaining supplied dimensions' is slightly opaque out of context but still earns its place as a behavioral guarantee.

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?

For a single-parameter, closed-world, read-only list tool with no output schema, the description covers purpose, defaulting behavior, submission-time validation, and the user-interaction policy. Nothing an agent needs in order to decide to call it or to interpret its role is 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?

Only the `asset` parameter exists and the schema documents it at 100% coverage, so the baseline is 3. The description adds no meaning about the asset argument (scope, symbol format, or what an invalid symbol does), so it does not exceed that baseline.

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?

States a specific verb and resource: list 'execution venue and quote-token choices for a backtest'. That is concrete enough to distinguish it from list_backtests or list_exchanges, though it never explicitly contrasts itself with the similarly named list_sweep_markets, leaving the agent to infer the sweeps-vs-backtests split.

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

Usage Guidelines4/5

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

Gives clear when-to-use ('Use when the user asks for alternatives') and an explicit when-not-to ('Do not ask for a market choice unless the user requests one'), plus reassurance that omissions are auto-resolved. Missing only an explicit pointer to a sibling alternative for the sweep case.

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

All MangroveAI 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