Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USTB

Paid. Invesco Short Duration US Government Securities Fund (USTB) 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/USTB.

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

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 a solid job: it discloses the paid cost and currency, accepted chains, that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. These are exactly the operational traits an agent needs before spending money. The main omissions are rate limits, latency, and what a failure response looks like.

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?

Front-loaded with the single most decision-relevant fact ('Paid'), then purpose, then cost and access terms, then the endpoint. Two sentences carry a lot of information with no filler. The raw URL is of marginal value to an agent invoking a tool by name, but it is a single token and not disruptive.

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, no-annotation, no-output-schema tool, the description covers cost, authentication, failure semantics, and the returned fields, which is most of what an agent needs. The residual gap is sibling disambiguation against buy_yields_token_ustb, which matters given the size of this catalog.

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 nothing for the description to disambiguate; baseline 4 applies. The only arguable parameter is the implicit token identity and payment chain, and the description does state the chain options (Base or Solana).

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 a specific resource (Invesco Short Duration US Government Securities Fund / USTB) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is far beyond a tautology. It loses a point because the sibling list also contains buy_yields_token_ustb and buy_yields_protocol_invesco-ustb for the same asset, and the description never distinguishes a spot-price call from a yields call.

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 token-specific naming and the 'Paid' lead, and the cost/payment details ($0.01 USDC on Base or Solana) help an agent decide whether it can afford to call. However there is no explicit when-to-use or when-not-to-use statement, and no routing to the near-identical USTB yield siblings, so the agent must infer the 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