Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS ASTRA Scorecard

mnemos_astra_scorecard
Read-onlyIdempotent

Free. Public methodology and prospective signal observations. Not user P&L. Annotation basis: readOnlyHint=True (reads a published scorecard, mutates nothing), idempotentHint=True, destructiveHint=False, openWorldHint=True.

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

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?

Most of the behavioral sentence re-states the supplied annotations ('readOnlyHint=True... idempotentHint=True, destructiveHint=False, openWorldHint=True'), which earns no credit per the rubric. The genuinely additive parts are 'Free' (no cost/quota barrier), 'public methodology' (data provenance) and 'Not user P&L' (scope of returned data excludes personal records) — useful, but thin given annotations already cover the safety profile.

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?

Short and front-loaded: 'Free' and the data-scope disclaimer come before the annotation recap. The annotation-restating parenthetical is redundant with structured fields and could be dropped without losing information, which keeps it off a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument, read-only tool the definition is nearly sufficient, but with no output schema the agent has no idea what a 'scorecard' returns — sections, metrics, freshness, or format are all unstated. One clause on the response shape would close the gap.

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 takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a published scorecard of 'public methodology and prospective signal observations' and rules out personal P&L, which helps distinguish it from account-oriented siblings. However, there is no verb describing what the tool does (retrieve? render? compute?) and 'scorecard' is never unpacked, so the agent knows the topic but not the action or content.

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?

'Free' and 'public' imply this is an unauthenticated, no-quota call, and 'Not user P&L' implies it is not the tool for personal performance data. But there is no explicit when-to-use statement, no named alternative among the siblings, and no condition that selects this tool over mnemos_status or mnemos_decisions.

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