Skip to main content
Glama
Sign In
Blocksize Market Data

Blocksize Market Data

by jf-cmyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Live Data Endpoint Builder

get_market_data_endpoint

Prepare a paid HTTP endpoint URL for live market data like VWAP, bid/ask, FX, or metal prices using a symbol, without executing the request or initiating payment.

Instructions

Build a paid x402 HTTP endpoint URL without calling it or starting payment.

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": {
      "service": "<service>",
      "symbol": "<symbol>"
    },
    "name": "get_market_data_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesExact paid HTTP symbol, such as BTC-USD, EURUSD, XAUUSD, or MSOLUSD.
serviceYesLive HTTP data service to prepare. Use state for /v1/state/{pair}.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, description carries full burden. It clearly states no side effects: does not call endpoint or initiate payment. This is sufficient for a non-destructive URL builder tool.

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?

Single sentence of 11 words, front-loaded with action verb. Every word earns its place.

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?

Output schema exists to document return structure. Description sufficiently defines purpose and non-side-effect behavior for a low-complexity tool with 2 parameters.

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% with clear descriptions for both parameters. Description adds no extra parameter information, so baseline score of 3 is appropriate.

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?

Description uses specific verb 'Build' and resource 'paid x402 HTTP endpoint URL', clearly distinguishing from sibling tools like 'fetch' which would call the endpoint. Scope is explicit: builds URL without executing or starting payment.

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

Usage Guidelines3/5

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

Implies use case: preparing a URL before fetching. But lacks explicit guidance on when to use this vs siblings (e.g., fetch, get_pricing_info). No exclusions or alternatives mentioned.

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

Deploy Server

Other Tools