Skip to main content
Glama

AgentHC Market Intelligence

get_market_snapshot

Real-time market snapshot: indices, volatility, yields, commodities, crypto, sentiment, and market regime.

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

Input Schema

NameRequiredDescriptionDefault
formatNoResponse format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.full
include_promptNoInclude formatted text for LLM prompt injection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "full",
      +  "description": "Response format. 'agent' returns actionable signals, urgency, delta tracking, and suggested follow-ups.",
      +  "enum": [
      +    "full",
      +    "compact",
      +    "prompt",
      +    "agent"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It contributes only 'Real-time', leaving unstated whether the call is cheap or rate-limited, how fresh or cached the data is, what market coverage (US vs global) applies, and what happens if a feed is unavailable — significant gaps for a data-aggregation tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler; the domain list earns its place by scoping what 'snapshot' contains. It is a noun phrase rather than a full clause, but that costs little clarity.

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 zero-required-parameter read tool with no output schema and fully documented inputs, the description covers what the tool returns at a domain level. The remaining gap is specificity — 'market regime' and 'sentiment' are undefined and market/asset coverage is unstated — but nothing essential to invoke it correctly is missing.

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 description coverage is 100% and both the 'format' enum values and 'include_prompt' are already documented in the schema, so the baseline of 3 applies. The description adds no further meaning about how format choices change the payload or when 'agent'/'prompt' modes are preferable.

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?

Names a specific resource ('market snapshot') and enumerates the exact data domains returned (indices, volatility, yields, commodities, crypto, sentiment, market regime), so an agent knows this is a broad aggregate rather than a single-asset feed. However it never explicitly contrasts itself with siblings like get_crypto_data or get_news_sentiment, leaving the differentiation implicit in the domain list.

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, no named alternatives, and no prerequisites or caveats. The only usage signal is the word 'snapshot', which hints at a broad overview but never says to prefer this over the narrower sibling tools for specific asset classes.

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