Skip to main content
Glama

U.S. Market Regime

start_blind_chart_drill

Read-onlyIdempotent

Return an instant zero-login masked-ticker historical U.S. stock bar-by-bar practice session URL, structured execution protocol, and $0 Pre-Market Checklist link.

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": "start_blind_chart_drill"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoExecution skill to focus on during the blind historical drill.stop_discipline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context ('zero-login', 'masked-ticker', 'instant') and names the three artifacts returned. It does not say whether repeat calls return the same session (relevant despite idempotentHint) or whether sessions expire.

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?

One front-loaded sentence with no filler sentences. Minor deduction for promotional idioms ('instant zero-login', '$0') that add tone rather than information an agent needs to call the tool.

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?

With one optional param, no output schema, and a rich annotation set, the description is nearly complete: it explains what is produced (URL, protocol, checklist link). It still leaves the agent without guidance on how the focus enum changes the returned session and whether calls are meant to be repeated.

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 focus enum values are documented in the schema with a description, so the schema carries the semantics. The description never mentions the focus parameter or its effect on the drill, so it adds no meaning beyond the structured field.

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?

States a concrete action and its outputs: returns a masked-ticker historical bar-by-bar practice session URL, an execution protocol, and a checklist link. The resource (blind chart replay drill) is specific and not confusable with the drawdown or regime siblings. It loses a point only because the phrasing is dense and bundles three outputs into one sentence.

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?

There is no when-to-use or when-not-to-use guidance. 'Practice session' and 'blind historical drill' imply a training context, but nothing tells an agent when to choose this over other tools or what precondition (if any) triggers it.

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.