Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SERV

Paid. OpenServ (SERV) 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/SERV.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full disclosure burden, and it does meaningful work: it declares the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no credentials are needed, and that failed calls are not charged. That failure-and-billing policy is exactly the kind of context annotations would otherwise supply. It stops short of a 4-5 because nothing is said about rate limits, response latency, or what a 'failed call' means (HTTP error vs empty result).

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 'Paid.' so the cost model is the first thing the agent sees, then follows with what is returned and how payment works. The telegraphic phrasing packs a lot into five short clauses with no filler, though the trailing raw URL is marginal value for an agent that already has the endpoint wired up.

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 tool, the essentials are covered: what data comes back, what it costs, where to pay, that failure is free, and that no auth setup is needed. The remaining gap is that the return shape (field names, units for market-cap rank) is unspecified, but with no output schema this is a minor omission rather than a blocker.

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 schema has zero parameters, which sets the baseline at 4. The description usefully confirms the no-input contract by stating 'No account, no API key', so an agent will not go hunting for credential or symbol arguments.

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 (OpenServ / SERV token price) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. An agent knows precisely what this tool fetches. It falls short of a 5 because it never distinguishes itself from adjacent siblings such as buy_crypto_price or the buy_coin_* family, which plausibly overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states access conditions ('No account, no API key') but gives no when-to-use guidance, no when-not-to-use, and no pointer to an alternative tool for general price lookups versus this single-token endpoint. An agent must infer selection purely from the token symbol in the tool name.

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