Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Arbitrage Scan

mnemos_arb_scan
Read-onlyIdempotent

Paid (x402, 0.001 USD). Runs the cross-venue arbitrage scan and returns the arb module's verdict: the module name, its stated reason, and whether it abstained (no qualifying opportunity found). Takes no inputs besides payment_signature; without a valid payment proof the call returns the route's 402 payment requirements.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mnemos_arb_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_signatureNoCaller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds material context beyond them: the per-call cost, the payment-gated failure mode (402 requirements returned instead of results), and the abstention outcome meaning no qualifying opportunity. These are exactly the behavioral facts an agent needs before spending money on a call.

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?

Three tight sentences, cost and payment gating front-loaded, then the return contract. No filler or restatement of the title.

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?

With no output schema, the description carries the burden of return values and does so (module name, reason, abstention). It omits freshness/caching or rate-limit expectations, which is a minor gap for a paid scan with an idempotency hint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already explains that omitting payment_signature yields payment requirements, so the baseline is 3. The description adds the price point and frames the parameter as a payment proof, giving slightly more meaning than the schema alone.

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?

The description names a specific verb and resource ('Runs the cross-venue arbitrage scan') and even specifies the return shape (module name, stated reason, abstention flag), so an agent knows exactly what it gets. It never names a sibling or states how it differs from mnemos_options_scan, so it falls short of a 5.

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 concrete invocation context: the call is paid (x402, 0.001 USD), takes no inputs besides payment_signature, and without valid payment proof returns the route's 402 requirements. There is no explicit when-to-use versus alternatives guidance, so 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources