Skip to main content
Glama

Tokenized-Stock Supply Payment Quote

tokenized_equity_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/tokenized-equity (base $0.005; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?symbol=AAPLx or ?contract=0x9d275685dc284c8eb1c79f6aba7a63dc75ec890a (optional chain=ethereum|hyperevm). Onchain totalSupply only.. Onchain totalSupply for one seeded tokenized-stock entry by symbol or contract: issuer, underlying ticker, chain, contract, decimals, and the custodian named on the issuer page, with source URLs. Seed: Ondo, xStocks/Backed, Dinari. Supply is not a share count or a price. Unknown entry, bad input or RPC down: not charged. USDC on Base only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: pricing ($0.005 base, USDC on Base only) and the guarantee that 'Unknown entry, bad input or RPC down: not charged.' It does not clearly describe what the tool itself returns, since the field list reads as the downstream API's payload.

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

Conciseness2/5

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

The text is a run-on with duplicated content: 'Onchain totalSupply only..' appears twice and 'USDC on Base only' is stated twice, plus an inline URL and pricing in the first clause. The core distinction (this tool quotes terms, it does not fetch supply) is buried mid-paragraph rather than front-loaded.

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

Completeness3/5

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

For a zero-parameter quote tool with no output schema, it does cover price, payment protocol, error non-charging, and a rough field list, which is enough to call it. However, the conflation of endpoint query parameters with tool inputs and the uncertain distinction between the quote result and the paid data leave a real gap for an agent deciding what it will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero properties, yet the description introduces 'GET ?symbol=AAPLx or ?contract=0x9d... (optional chain=ethereum|hyperevm)', which an agent may read as tool arguments that will then fail schema validation. It is framed as HTTP query syntax, but the mixing of endpoint parameters into an empty-schema tool confuses rather than clarifies.

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

Purpose3/5

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

The opening sentence identifies a specific verb and resource ('Returns the payment terms for .../api/tokenized-equity'), but the description then describes what the paid endpoint returns ('Onchain totalSupply ... issuer, underlying ticker, chain, contract, decimals, and the custodian'), blurring whether this tool returns a price quote or the supply data. It never names or contrasts any sibling (e.g. tokenized_stock or http), so the agent must guess which tool to pick.

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?

The description gives real usage context: pay the 402 over HTTP with x402 v2, and it states the tool itself 'never runs the check or pays', which implies it is a pure quote step. But it gives no explicit when-to-use vs. when-not-to-use against the many sibling '*_quote' tools, and the ordering between this quote and the actual HTTP call is left for the agent to infer.

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.