Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ADS

Paid. Adshares (ADS) 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/ADS.

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

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 supplied, the description carries the full burden and does a solid job: it discloses cost ($0.01 USDC), payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — an unusually useful billing guarantee for an agent deciding whether to retry. It omits return format/payload shape and any rate limits or latency expectations.

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 signal lands first, then payload, then price/auth/billing, then endpoint. No filler sentences. The staccato fragment style is slightly harder to parse than prose, but each fragment carries distinct operational information.

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?

With no output schema, the description compensates by enumerating the returned fields (live USD price, 24h change, market-cap rank), which is exactly what an agent needs to judge relevance. Cost, payment rail, auth model, failure billing, and endpoint are all covered; only return format specifics and rate limits are missing, which are minor for a zero-parameter read.

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 the baseline is 4. The description reinforces this by stating 'No account, no API key', telling the agent no auth parameter or credential setup is needed before calling. There is nothing further to document on the input side.

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 and payload: 'Adshares (ADS) price: live USD price, 24h change and market-cap rank'. The ticker is embedded in both name and description, so an agent can tell it apart from the hundreds of sibling buy_tok_*/buy_coin_* entries without opening a schema. It stops short of explicitly contrasting itself with buy_crypto_price, which is the one genuinely ambiguous alternative.

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 rather than stated: a paid lookup for ADS spot price data. There is no explicit 'use this when…' or 'do not use this if…', and no sibling is named as an alternative for other assets or for non-price ADS data. The 'Paid' opener at least signals this is a metered call, which is the main decision an agent has to make.

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