Skip to main content
Glama

Market state

market_context
Read-only

Market-wide context: Market Pulse (share of top coins trending up on 1D and 4H), volatility state, Fear & Greed with its attribution, and the BTC 1D / 4H trend. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and data provenance are covered. The description adds useful behavioral facts beyond that: the composite nature of Market Pulse (defined as share of top coins trending up), the attribution carried with Fear & Greed, and that the call is free. It omits freshness/caching behavior, snapshot vs streaming, and how the composite is weighted.

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?

One sentence, front-loaded with the scope ('Market-wide context') followed by the enumerated payload, with inline parentheticals defining the non-obvious term. No filler or hedging.

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 and no output schema, the description carries the burden of describing the payload, and it does list all four returned components. It stops short of giving units or value formats (e.g. whether Market Pulse is a percentage, how volatility state is expressed), which would matter for a tool whose entire value is its return data.

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 no parameters, so there is nothing for the description to compensate for. Baseline 4 applies; the description correctly spends no words on arguments.

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 names a specific resource and enumerates exactly what it covers: Market Pulse (share of top coins trending up on 1D and 4H), volatility state, Fear & Greed with attribution, and the BTC 1D/4H trend. 'Market-wide context' implicitly distinguishes it from per-asset siblings like get_price, but no sibling is named explicitly, leaving the differentiation to inference.

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 framing, no exclusions, and no routing to alternatives such as get_analysis or range_stats. The only usage-adjacent signal is the trailing 'Free', which hints at cost but not at selection between tools.

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