Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_sweep_run

Read-onlyIdempotent

One run rebuilt as the strategy it was, entry and exit rules with the parameter values the engine drew. This is the way OUT of a sweep: a row worth acting on becomes a saved strategy and then a real backtest over a window the person chose. Reach for it once a row is interesting, not for every row in a ranking.

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": {
      "experiment_id": "<experiment_id>",
      "run_index": "<run_index>"
    },
    "name": "get_sweep_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_indexYesWhich run, as find_sweep_runs reported it.
config_hashNoThe row's config_hash, as find_sweep_runs reported it. Pass it whenever you have it: a relaunched sweep can give one run_index to several runs, and without it such an index is refused, not guessed.
experiment_idYesThe sweep, as create_sweep returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds useful workflow context about what the return enables: turning a row into a saved strategy and a backtest over a chosen window. It doesn't describe response shape or failure modes, but for a read tool with full annotation coverage this is solid added value.

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?

Payload is front-loaded in the first sentence and the usage rule follows immediately. The prose is slightly flowery ('the strategy it was', 'way OUT of a sweep') but every sentence contributes and nothing is repeated.

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?

There is no output schema, and the description does communicate what comes back: entry and exit rules plus the parameter values the engine drew. Combined with the usage guidance and full schema coverage, an agent has what it needs, though a bit more on the returned object's shape would close the remaining gap.

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 description coverage is 100%, and the schema already explains the config_hash safety rule and the sourcing of experiment_id and run_index. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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: it returns one sweep run rebuilt as its strategy, including entry and exit rules with the drawn parameter values. The poetic 'rebuilt as the strategy it was' is a bit indirect, but an agent can tell it apart from find_sweep_runs and get_sweep, which are referenced in the schema.

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?

Explicitly says when to use it: 'Reach for it once a row is interesting, not for every row in a ranking', which implicitly routes per-row enumeration to find_sweep_runs. It also names the follow-on path (save_strategy then a real backtest). No explicit when-not case or sibling name in the description, so it falls short of a 5.

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