Skip to main content
Glama

SouthPow crypto & market data

buy_tok_TSLAX

Paid. Tesla xStock (TSLAX) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/TSLAX.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well on the dimensions that matter for a paid endpoint: it declares the price ($0.01 USDC), the accepted settlement chains (Base or Solana), that no account/API key is required, and that failures are not billed. It stops short of disclosing rate limits, freshness/latency of the quoted price, or what a successful response body looks like, which are the remaining behavioral unknowns.

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

Conciseness4/5

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

Tight and front-loaded: 'Paid.' and the asset name lead, followed by payload, cost, auth, billing policy, and endpoint. Every clause carries information an agent needs before calling a paid tool. The trailing raw URL is of marginal value to an agent that already has the tool registered, which keeps it from a 5.

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 zero-parameter, annotation-free paid lookup, the description covers what the agent needs: what is returned, what it costs, how it is paid for, and that failures are free. Because there is no output schema, naming the three returned fields is doing the necessary work. Only the response shape and data freshness are left implicit.

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 zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly signals this by naming the asset inline (TSLAX) rather than implying any caller-side 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?

States a specific resource (Tesla xStock TSLAX price) and the exact payload (live USD price, 24h change, market-cap rank), so it is clearly distinguishable from generic siblings like buy_crypto_price or buy_tok_NVDA. It does not, however, explain how it differs from near-identical tokenized-stock variants in the same family (buy_tok_TSLAON, buy_tok_TSLAB, buy_tok_TSLAX-adjacent listings), which is the one differentiation an agent might actually need.

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 implies usage through the pricing and payment model ('$0.01 USDC on Base or Solana. No account, no API key'), but never says when to pick this over the many alternative Tesla/price tools or what conditions make it the wrong choice. The 'Failed calls not charged' clause is the closest thing to selection guidance, and it addresses cost risk rather than tool choice.

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