Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

evaluate_strategy

Evaluate a saved strategy against current live market data to check if entry or exit signals are firing right now. Returns the current asset price and any order intents the signals would produce. It places no orders and opens no positions, but each call records the evaluation: it updates the strategy's last_evaluated_at and evaluation_count and adds an agent_evaluations audit row. Use it when the user asks whether a strategy should be entering or exiting at this moment, or wants the live signal state for a specific strategy. Over x402, a wallet that proves its identity (Sign-In-With-X) gets 30 evaluations free per UTC day, then 0.05 USDC each; an API key is covered by its plan.

[Access: pay 0.05 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": "evaluate_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.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the call places no orders but mutates state — updating last_evaluated_at and evaluation_count and inserting an agent_evaluations audit row — which explains the readOnlyHint=false and idempotentHint=false. It also details the x402 free-tier quota and per-call pricing, a rare and useful disclosure; it does not cover failure modes or latency, keeping it short of a 5.

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 purpose, then side effects, then usage, then cost — a sensible order with no filler. The bracketed access note repeats the x402/API-key information already given in the preceding sentence, a small redundancy.

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 payload (asset price plus order intents), the audit side effect, the usage trigger, and the payment/auth path. Nothing an agent needs before calling this single-parameter tool 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 one parameter, already documented at 100% schema coverage ('The strategy's UUID'). The description adds the idea that it must be a saved strategy, but nothing about ID format, lookup failure, or validation — baseline 3 applies.

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 (evaluate a saved strategy) plus the exact question it answers: whether entry or exit signals are firing right now. It also declares what is returned (current asset price and order intents), which separates it from signal-level siblings like evaluate_signal.

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 an explicit trigger: 'when the user asks whether a strategy should be entering or exiting at this moment, or wants the live signal state for a specific strategy.' It does not name alternatives (evaluate_signal, evaluate_multiple_signals_series, verify_strategy) or state when not to use it, so routing still requires inference.

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