Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Ensemble Decisions

mnemos_decisions
Read-onlyIdempotent

Paid (x402, 0.001 USD). Returns the MNEMOS ensemble's latest decision output — the current decision set produced by the engine's signal modules. Takes no inputs besides the caller's payment_signature; without a valid payment proof the call returns the route's 402 payment requirements. Read-only: it reports stored decision output and places no orders.

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

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds valuable behavior beyond annotations: paid access via x402 at 0.001 USD, the 402 fallback when payment proof is missing or invalid, and explicit confirmation that no orders are placed. Rate limits or response timing are not covered, but the important payment and read-only behavior is well disclosed.

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?

The description is three tight sentences that front-load paid status, then state what is returned, then clarify input and read-only behavior. There is minor redundancy with the schema around returning 402 requirements when payment is omitted, but the text remains efficient and well ordered.

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 retrieval tool with no output schema and rich annotations, the description is largely complete: it covers payment, the 402 failure mode, the nature of the returned decision output, and confirms no orders are placed. It does not describe the structure or contents of the decision set, and it gives no sibling selection guidance, which are minor gaps rather than blockers.

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?

There is only one parameter, payment_signature, and schema description coverage is 100%. The schema already explains that it is a caller-supplied x402 v2 PAYMENT-SIGNATURE and that omitting it returns payment requirements. The description adds the consequence of an invalid proof yielding a 402 response, but otherwise adds little meaning beyond the schema.

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 states a specific resource and operation: it returns the MNEMOS ensemble's latest decision output, described as the current decision set produced by the engine's signal modules. This is clear enough to distinguish it from generic status or scan tools by content, but it does not explicitly differentiate itself from siblings such as mnemos_status or mnemos_options_cached.

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

Usage Guidelines2/5

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

The description explains payment mechanics, including that omitting payment_signature returns 402 payment requirements, but it gives no when-to-use guidance relative to alternatives. It does not say when an agent should call this instead of mnemos_status, mnemos_arb_scan, or any other sibling, nor does it state exclusions.

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