Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OVER

Paid. Overtime (OVER) 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/OVER.

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

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, the description carries the full burden and does a good job: it discloses cost ($0.01), accepted payment rails (Base or Solana), that no account or API key is required, and that failed calls are not charged — a genuinely useful failure-billing guarantee. It omits response shape and data freshness/caching, but the core economic and auth behavior is well covered.

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?

Seven terse fragments, front-loaded with 'Paid.' so the agent sees the cost model before anything else. Every fragment carries information (data returned, price, rails, auth, billing on failure, URL) with no filler, though the telegraphic style is slightly dense.

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 paid data endpoint with no output schema, the definition covers what an agent needs to decide and call: what data comes back, what it costs, how to pay, and that failures are free. The only real gap is that response format and update cadence are unspecified, which matters somewhat since there is no output schema.

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; baseline for a no-param tool is 4. The description correctly implies the token symbol is baked into the endpoint rather than passed as an argument.

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 the specific resource ('Overtime (OVER) price') and enumerates the returned fields: live USD price, 24h change and market-cap rank. An agent can tell what data it gets without opening anything. It does not, however, distinguish itself from adjacent siblings like buy_crypto_price or the many buy_coin_* variants, so the section is clear but not sibling-differentiating.

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 gives useful purchase context (paid, $0.01 USDC on Base or Solana, no account or API key) that implies this is a pay-per-call data fetch. But it never says when to choose this over buy_crypto_price or buy_coin_OVER-style alternatives, and offers no exclusions or prerequisites beyond payment.

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