Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Engine Status

mnemos_status
Read-onlyIdempotent

Free. Live engine status: mode, watchlist, scan freshness, scorecard summary. Annotation basis: readOnlyHint=True (reads current state, mutates nothing), idempotentHint=True (repeated calls are equivalent reads), destructiveHint=False, openWorldHint=True (reflects live external market state).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description restates those hints with brief parenthetical explanations and adds that the tool is free and reflects live external market state, but it does not add operational details such as rate limits, auth needs, or return behavior beyond the field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the useful purpose and status fields. However, the second sentence largely repeats the structured annotations, so it does not fully earn its place even though the overall length is modest.

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 parameters, no output schema, and rich annotations, the description is complete enough for an agent to understand that this is a safe, idempotent status read. It lists the status components an agent would receive, though it could say more about when to prefer this over sibling tools.

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?

The tool has zero parameters, so there is no parameter semantics to document. The baseline for a no-parameter tool is 4, and the description does not introduce confusion about inputs.

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, "Live engine status," and enumerates the status components: mode, watchlist, scan freshness, and scorecard summary. This distinguishes it from siblings like mnemos_arb_scan and mnemos_astra_scorecard, though it does not explicitly route the agent between them.

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 only usage context is "Free" and the implication that it reports current engine state. There is no explicit guidance on when to call this versus the scan, scorecard, decisions, gas, or options siblings, and no when-not conditions.

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