Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USTBL

Paid. Spiko US T-Bills Money Market Fund (USTBL) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/USTBL.

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

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?

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses the paid cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no auth is needed, and that failed calls are not charged — the last being genuinely important for an agent deciding whether to retry. What it omits is latency/response-shape behavior and what happens on partial payment failure.

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?

Six short clauses, front-loaded with 'Paid.' so the agent sees the cost gate before anything else, followed by purpose, then price, then mechanics. Every sentence earns its place except the raw endpoint URL, which duplicates machine-level routing information an agent does not act on.

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?

With no output schema and no annotations, the description has to carry the return-value burden itself, and it does by naming the three fields returned. For a zero-parameter paid endpoint that is close to complete; only freshness/cadence of the 'live' price is left unstated.

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 is 4. The description correctly spends its words on the asset identity and return fields instead of inventing parameter guidance.

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?

The description names the specific asset (Spiko US T-Bills Money Market Fund, ticker USTBL) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. That is a concrete verb+resource statement. It falls short of 5 because it never distinguishes itself from the near-identical siblings buy_tok_USTB, buy_yields_token_ustb, or buy_tok_EUTBL, so an agent still has to infer which of those 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?

Usage is implied by the content — call this when you need USTBL spot price data — and the 'No account, no API key' line removes a precondition an agent might otherwise worry about. But there is no explicit when-to-use/when-not clause and no pointer to an alternative for historical or yield data, which is exactly the ambiguity created by the many ustb-adjacent siblings.

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