Skip to main content
Glama

get_market_data

FREE for the delayed sample; the endpoint's x402 price applies for live data (from $0.001/call). Fetch data from an endpoint returned by search_market_data. Without a subscription this returns a REAL but delayed sample at no cost — enough to see the exact response shape and judge the data. With an active subscription key it returns live data. Live data is also purchasable per call in USDC over x402 at https://api.losbeto.xyz.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint": "<endpoint>"
    },
    "name": "get_market_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoQuery parameters, e.g. {"symbol": "PETR4"}.
endpointYesEndpoint path, e.g. '/br-macro' or '/oracle-consensus'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the auth model (subscription key vs none), the cost model ($0.001/call x402 in USDC), and crucially that the free path returns real-but-delayed data in the exact response shape. Missing are failure modes, rate limits, and pagination/size expectations.

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

Conciseness3/5

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

The pricing caveat is repeated three times in different words (free delayed sample, no-cost delayed sample, $0.001/call live), which crowds out what the tool actually returns. Front-loading price before the core action also delays the agent's primary signal, though the search_market_data reference does appear early.

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 2-parameter tool with no output schema and a nested params object, the description supplies the two things an agent most needs: where 'endpoint' comes from and what data quality/cost to expect. Return values need not be explained since the description notes the sample reveals the exact response shape, but error and quota behavior remain unaddressed.

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 properties are documented there, including examples, so the baseline is 3. The description adds only the provenance rule for 'endpoint' (must come from search_market_data) and says nothing about the free-form 'params' object beyond what the schema example covers.

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 specific verb and resource ('Fetch data from an endpoint'), and ties the input to the output of a named sibling (search_market_data), which cleanly separates discovery from retrieval. It does not explicitly name the other siblings (market_snapshot, list_categories), but the search-then-fetch workflow makes the distinction clear.

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?

Gives a clear precondition (endpoint must come from search_market_data) and a clear tiering rule: no subscription returns a delayed sample, an active subscription key returns live data. It stops short of stating when-not to call it (e.g., use market_snapshot for quick quotes) but the context is strong enough for correct selection.

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