Skip to main content
Glama

SouthPow crypto & market data

buy_tok_THBILL

Paid. Theo Short Duration US Treasury Fund (THBILL) 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/THBILL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 more than most: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. Missing only rate limits, caching/freshness of the quoted price, and failure/refund semantics beyond the free-failure note.

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

Conciseness5/5

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

Front-loaded billing status ('Paid.') immediately flags that invoking costs money, followed by purpose, response fields, price, payment rails, and trust signals. Six short clauses, each earning its place, with no filler.

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-param, no-output-schema paid price endpoint, the description covers what is returned (price, 24h change, rank), the cost, how to pay, and the failure policy — enough for an agent to decide and call. It could be richer on data freshness and the concrete response shape, but nothing essential is missing.

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 the baseline of 4 applies; there is nothing for the description to disambiguate. The token and endpoint are hard-coded and the URL is given, which is the only parameter-like information an agent could need.

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 and the exact data returned: live USD price, 24h change and market-cap rank for the Theo Short Duration US Treasury Fund (THBILL). An agent can tell what it fetches. However, it never differentiates from the large family of near-duplicate siblings (buy_tok_USTBL, buy_tok_VBILL, buy_stable_*, buy_yields_token_ustb, buy_crypto_price), so sibling disambiguation is left to the name alone.

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 context is implicit but inferable: this is the paid per-token price lookup for THBILL, requiring $0.01 USDC on Base or Solana. There is no explicit when-to-use vs when-to-use-an-alternative statement, and given the hundreds of overlapping price/token/yield siblings, an explicit routing sentence would materially help.

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