Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SYN

Paid. Synapse (SYN) 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/SYN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 well: it discloses that the call is paid, the exact price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of stating rate limits, response latency, or what a billing failure looks like.

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?

Two tight sentences, front-loaded with the 'Paid' caveat so the agent sees the cost before anything else, then the payload, then the payment mechanics. Every clause (chains, no API key, no charge on failure) carries distinct decision-relevant 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?

For a zero-parameter, output-schema-less price lookup, the description covers what comes back (three named fields), what it costs, how to pay, and the failure policy, which is enough to invoke it correctly. Missing only finer return-shape detail such as field names or update cadence.

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 the baseline applies; there is nothing for the description to disambiguate. The token symbol is baked into the endpoint path, which the description makes visible, so the agent knows no input is required.

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 concrete resource ('Synapse (SYN) price') and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. It does not explain how it differs from the very similar buy_coin_SNX / buy_crypto_price siblings, so an agent cannot route between them from this text alone.

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 only implied via the 'Paid' framing and the price of entry; there is no explicit statement of when to pick this over buy_crypto_price or a buy_coin_* equivalent, and no guidance on caching or repeated calls. The payment prerequisites are stated, which is the main practical selection criterion, but alternatives are never named.

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