Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Options Radar Scan

mnemos_options_scan

Paid (x402, 0.001 USD). On-demand fresh options-radar scan. Annotation basis: readOnlyHint=False because each call triggers a new scan rather than reading a stored result; idempotentHint=False because repeated calls can return different results and incur a new charge.

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_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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, but the description adds real context beyond them: a concrete cost (0.001 USD), the x402 payment protocol, and the fact that repeat calls incur a new charge. The 'annotation basis' sentences partly restate the annotation rationale rather than adding new facts, and openWorldHint is never addressed, so it falls 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?

Three short sentences with the most decision-relevant fact (paid, with price) front-loaded. The 'Annotation basis:' framing is slightly meta and consumes space that could have gone to when-to-use guidance, but nothing is padded.

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?

For a one-parameter, no-output-schema tool, the definition covers cost, payment flow, and freshness, which are the things an agent needs before calling. It is thin on failure behavior when payment is rejected or absent, but that gap is minor at this complexity level.

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 already documented in the schema, including the 'omit to receive payment requirements' behavior. The description contributes the price and protocol name but no additional semantics about the signature itself, so the baseline 3 applies.

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 resource and mode: an 'on-demand fresh options-radar scan'. The word 'fresh' implicitly contrasts with the stored-result sibling (mnemos_options_cached), so an agent can infer the distinction, but the sibling is never named explicitly, which keeps it from 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 Guidelines3/5

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

Usage is only implied through 'on-demand fresh' — an agent can reason that this is for live rather than cached reads, but the description never states when to prefer it over mnemos_options_cached or mnemos_arb_scan, nor any exclusion or prerequisite beyond the price.

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