Skip to main content
Glama

Tokenized stocks

tokenized_stocks

Tokenized stocks on Solana (xStocks): which tokens are the issuer's (mint authority read on chain), price, liquidity, volume; with a symbol, a $1,000 buy and sell quote (round-trip cost) and the look-alike fake tokens. $0.005

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_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNooptional ticker: AAPL, TSLA, SPY, NVDA...
paymentNoa signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose real behavior: on-chain mint-authority reads, the returned metrics, fake-token detection, and a '$0.005' price hinting this is a paid x402 endpoint. It does not state whether unpaid calls return partial data, how the payment gate behaves, or output/pagination shape, so material gaps remain.

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?

Compact and front-loaded with the resource, but it is a sentence fragment with no verb, and the trailing '$0.005' is tacked on without a label, reading as an orphaned price tag rather than integrated information.

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 two-parameter lookup with no output schema and no annotations, the description covers the data domains returned and mentions the priced purchase model. It stops short of describing the response shape, what an unsymbolized call returns, and how payment failure surfaces, which an agent needs given zero structured behavioral metadata.

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%, so both parameters are already documented, and the baseline applies. The description adds marginal value by indicating the symbol drives a hypothetical $1,000 buy/sell round-trip quote, but it adds nothing about the payment parameter beyond what the schema text already explains.

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 the specific resource (tokenized stocks on Solana / xStocks) and enumerates what it returns: issuer/mint authority, price, liquidity, volume, round-trip quote and look-alike fakes. That is enough to distinguish it from generic siblings like token_lookup or arc_token_info, though the leading verb is missing so the reader must infer it is a lookup tool.

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 explicit when-to-use statement and no named alternative. The phrase 'with a symbol, a $1,000 buy and sell quote' only implies that supplying a symbol triggers a quote, and nothing says when to prefer this over impostor_check, token_lookup or arc_token_check, which cover overlapping ground.

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