Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EUTBL

Paid. Spiko EU T-Bills Money Market Fund (EUTBL) 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/EUTBL.

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

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 tool is paid, the exact price and accepted payment chains, that no auth/account is required, and the failure billing policy. It does not describe rate limits, response shape or latency, but the key operational facts an agent needs before spending money are present.

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 resource and the returned fields, then commercial terms, then the URL. The telegraphic phrasing ('Paid.', '$0.05 USDC on Base or Solana.') is efficient rather than wasteful; the raw endpoint URL is the only item of questionable value to an agent.

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-output-schema price lookup, the description lists the returned metrics, the cost, the payment rails and the auth requirements, which is nearly everything needed to call it correctly. Minor gaps remain around response format and whether the result is cached or real-time beyond the word 'live'.

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?

Zero parameters, so there is no schema semantics to add; the baseline for a no-param tool is 4. The description correctly implies the ticker is fixed by the tool itself rather than passed in, which is the only parameter-like information relevant here.

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 (Spiko EU T-Bills Money Market Fund, ticker EUTBL) and exactly what is returned: live USD price, 24h change and market-cap rank. The ticker in the tool name plus the fund name make it distinguishable within the very large buy_tok_* family, though the description never names a sibling it differs from.

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 (fetch the EUTBL price) and the payment terms ('$0.05 USDC on Base or Solana', 'No account, no API key', 'Failed calls not charged') tell the agent the cost and preconditions of calling. There is no guidance on when to prefer this over buy_crypto_price, buy_coin_* or buy_stable_* alternatives, and no exclusions.

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