Skip to main content
Glama

stox-mcp

by io.github.nirajagarwal

Market stress context

market_regime
Read-only

Where market stress sits right now: the dashboard's 8-indicator stance, each indicator's traffic-light band, the VIX 5-year percentile (the ONE input validated as predicting forward risk — blended composites tested worse), and the S2 stress-confirmation badge (SPY below its 40-week average AND VIX above its 80th percentile of the trailing year). Descriptive context, not a market call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and the description explicitly states 'Descriptive context, not a market call,' preventing the agent from over-interpreting the output. It also discloses the input-validation design (VIX percentile vs blended composites) and the S2 badge conditions. Moderate value over annotations, but not richly detailed.

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

Conciseness5/5

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

A dense, single-sentence description that front-loads the most important fact (current market stress), then enumerates the concrete outputs. Every clause adds information; no filler.

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

Completeness5/5

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

For a zero-parameter, read-only context tool with no output schema, the description covers what the tool is, what it contains, and importantly how to interpret it (not a market call). Nothing needed for correct invocation is missing.

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?

No parameters exist, so the description's job of defining parameters is vacuous. It adds context about what inputs were tested (VIX percentile) even though the tool itself takes none. Baseline 4 for zero params is appropriate here.

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

Purpose5/5

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

States a specific verb-resource pair (market stress context) and defines exact indicators (8-indicator stance, traffic-light bands, VIX 5-year percentile, S2 badge). Distinguishes from sibling tools by naming market stress context, which no other sibling covers.

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

Usage Guidelines4/5

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

Describes what the tool tells an agent (descriptive context, not a market call) and implicitly when it is relevant: whenever the agent needs current stress/regime context. It does not cite sibling alternatives or exclusions, but the scope is sufficiently clear for a zero-parameter, non-destructive context tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All stox-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool owns a distinct analytical niche: single-stock character, multi-ticker comparison, market regime, business peers, co-movement cluster, and universe screening. The only near-overlap (fingerprint's peer list vs peers) is explicitly resolved by describing peers as the deeper standalone lookup.

Naming Consistency3/5

All names are lowercase and stylistically consistent, but there is no verb_noun pattern: compare and screen are verbs while market_regime, peers, and theme_cluster are noun phrases. The mixed grammar is readable but not a strongly predictable naming convention.

Tool Count5/5

Six tools is tightly scoped for a stock-character research server; each tool covers a distinct user workflow and none feels redundant. The count is well within the ideal range and does not burden an agent with overlapping endpoints.

Completeness5/5

The set covers the full intended workflow: assess market context, inspect a single stock, compare tickers, identify true peers and co-movement groups, and screen the universe on every available metric. There are no obvious dead ends or missing operations for a read-only analytics domain.

Resources