Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Options Radar (Cached)

mnemos_options_cached
Read-onlyIdempotent

Paid (x402, 0.001 USD). Returns the cached options radar and anomaly intelligence from the most recent stored scan — the options activity and anomalies the desk has already computed, served without triggering a new scan. Takes no inputs besides payment_signature. Manual-desk research only; not advice.

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_options_cached"
  }
}

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.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely non-obvious traits: it is a paid x402 call at 0.001 USD, it serves a previously stored scan rather than computing, and the output is advisory research, not advice. It does not disclose how stale the cached scan may be or what the payload looks like, which are the remaining behavioral unknowns.

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-loads cost, then what is returned, then the caching behavior, then the advisory caveat — a sensible order. The em-dash gloss ('the options activity and anomalies the desk has already computed') partially restates the preceding noun phrase, a small redundancy in an otherwise tight description.

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 one optional parameter, no output schema, and annotations covering the safety profile, the description does what is needed: it explains the payment model, the cached nature, and the advisory framing. The notable gap is cache freshness — an agent cannot tell how recent the stored scan is, which matters for a market-intelligence tool.

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 payment_signature parameter is fully documented in the schema, including the omit-to-receive-payment-requirements handshake. The description only restates that there are no other inputs, adding little beyond the schema; baseline 3 is appropriate.

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 ('Returns') and a specific resource ('cached options radar and anomaly intelligence from the most recent stored scan'), and explicitly contrasts the behavior with a fresh scan ('served without triggering a new scan'), which is exactly what distinguishes it from mnemos_options_scan. An agent can tell the two apart without opening either 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?

Gives clear selection context: use it when you want already-computed desk output and do not want to trigger (or pay for) a new scan, plus an explicit scope restriction ('Manual-desk research only; not advice'). It stops short of naming mnemos_options_scan as the alternative for fresh data, so the routing is implied rather than stated.

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