Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PEOPLE

Paid. ConstitutionDAO (PEOPLE) 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/PEOPLE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 behavioral burden and does real work: it discloses the cost ($0.01 USDC), the accepted payment chains (Base or Solana), the absence of auth requirements, and a billing guarantee that failed calls are not charged. That is material information an agent cannot get from the empty schema. It does not explain the payment handshake itself (e.g., how the USDC is tendered) or any rate limits, which keeps it from a 5.

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?

Four short sentences, front-loaded with the paid/no-key/cost facts first and the payload description second. Every clause carries distinct information — cost, chains, auth, billing policy, endpoint — with no repetition of the tool name or fluff.

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 endpoint with no output schema, the description supplies both the shape of the returned data and the commercial terms, which is most of what an agent needs. What is missing is a note on the response encoding or whether the endpoint returns a single quote vs a history series, a minor gap given the listed fields.

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 semantics to clarify and nothing the description could add. Baseline 4 applies; the description correctly avoids inventing parameter-like options such as chain or currency selectors.

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?

The description names a specific resource (ConstitutionDAO/PEOPLE) and enumerates exactly what data comes back: live USD price, 24h change, market-cap rank. This is enough to tell it apart from the hundreds of buy_tok_* siblings, each of which targets a different token. It stops short of 5 only because the operative verb is implied ('price: ...') rather than stated, leaving the agent to infer that calling it purchases/returns the quote.

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?

There is no explicit when-to-use guidance and no routing to alternatives such as buy_crypto_price or the buy_coin_* family for the same asset. The only contextual hints are operational (no account, no API key, failures not charged), which help the agent decide it *can* call the tool but not whether it *should* versus a sibling.

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