Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

delete_strategy

Idempotent

Delete a strategy by its id. Strategies are NEVER hard-deleted: the service soft-archives the row, so the strategy and its history stay recoverable via unarchive. Use only when the person explicitly asks to delete or remove a strategy, and say plainly that it has been archived rather than implying it is gone.

[Access: pay 0.005 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "delete_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
strategy_idYesThe strategy's UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / strategy_id / description
      Added value: +"The strategy's UUID."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the row is never hard-deleted but soft-archived, history remains recoverable via unarchive, and the agent is told not to imply permanent deletion. The payment/auth model (0.005 USDC via x402 or API key, auto-pay for capable clients) is also disclosed, which the annotations say nothing about.

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?

Front-loaded with verb and resource, then the behavioral caveat, then the usage gate, then access mechanics — a sensible order. The bracketed payment paragraph is the longest element and slightly outweighs the operational content, but it is not padding.

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 one-parameter mutation with no output schema, the description covers effect, reversibility, required authorization, and cost model — everything an agent needs before invoking. Nothing material is left to inference.

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% and the single parameter is already documented as 'The strategy's UUID.' The description only restates 'by its id' and adds no format, sourcing, or lookup guidance beyond the schema. Baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb and resource ('Delete a strategy by its id') and immediately qualifies the semantics with the soft-archive behavior. Against siblings like get_strategy, update_strategy, list_strategies and save_strategy, an agent can tell exactly which operation this is.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('Use only when the person explicitly asks to delete or remove a strategy') plus the recovery path ('recoverable via unarchive'), so the agent knows both the trigger and the escape hatch. It also prescribes the user-facing phrasing, which is unusual but directly actionable.

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