Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

pause_sweep

Idempotent

Stop a running sweep from doing any more work, keeping every result it has already written. Use it when the person has seen enough, or when a search turned out far larger than they wanted. It does not undo what already ran, and the results stay readable afterwards -- so it is a way to stop spending, not a way to take it back. Say how many runs finished, which is what they keep. A sweep that was only QUEUED had not started, so stopping it returns it to validated rather than paused and it can be launched again later.

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>"
    },
    "name": "pause_sweep"
  }
}

Input Schema

NameRequiredDescriptionDefault
experiment_idYesThe sweep, as create_sweep returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations, the description discloses key behavioral traits: existing results are kept and remain readable, already-run work is not undone, and a QUEUED sweep transitions back to validated rather than paused. These details are valuable because they explain the non-destructive, idempotent nature of the operation in concrete terms rather than relying solely on hints.

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?

The description is front-loaded with the core action and then uses each sentence to add a distinct operational nuance: results are kept, this is not an undo, and QUEUED sweeps behave differently. There is no redundant or wasted text.

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?

With no output schema, the description still explains the return implication by saying to 'Say how many runs finished, which is what they keep.' It also covers the important QUEUED edge case and the non-destructive result, making the definition complete enough for correct invocation without requiring the agent to consult other fields.

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 single parameter is already documented as 'The sweep, as create_sweep returned it.' The description does not add further meaning about the experiment_id parameter itself, so the schema does the heavy lifting. Baseline 3 is appropriate for a one-parameter tool with full schema coverage.

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?

The description opens with a specific verb and resource: 'Stop a running sweep from doing any more work, keeping every result it has already written.' This clearly distinguishes pausing from deleting or undoing, and it identifies the scope precisely enough that an agent can separate it from siblings like launch_sweep, get_sweep, or find_sweep_runs.

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?

It gives clear when-to-use guidance: 'Use it when the person has seen enough, or when a search turned out far larger than they wanted.' It also distinguishes the QUEUED case, explaining that stopping an unstarted sweep returns it to validated rather than paused. It does not explicitly name a sibling alternative, but the contrast with 'take it back' sufficiently implies what this tool is not for.

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