Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOAT

Paid. Goatseus Maximus (GOAT) 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/GOAT.

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

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 behavioral burden and does so well: it declares the call is paid, the exact cost ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. That is precisely the context an agent needs before spending money. Remaining gaps are rate limits and response shape, which are minor here.

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-loads the critical constraint ("Paid.") before the resource, then packs cost, payment rails, and auth requirements into a handful of short clauses with no filler. The trailing URL is slightly redundant with the tool identity but is genuinely useful as an endpoint reference.

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 definition covers what is returned, what it costs, how to pay, and that no credentials are needed. An agent could invoke it correctly and predict the charge. Only the exact response payload structure is left implicit.

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?

There are zero input parameters, so the baseline of 4 applies. The description correctly indicates the asset is baked into the endpoint rather than passed as an argument, and even shows the concrete URL, so an agent knows no parameterization is possible or needed.

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 the specific asset (Goatseus Maximus / GOAT) and the exact data returned: live USD price, 24h change, and market-cap rank. An agent can tell this is a single-token price lookup rather than a general market tool. It stops short of distinguishing itself explicitly from the generalist buy_crypto_price sibling, which keeps it out of 5 territory.

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 implies the use case clearly (fetch GOAT price data) and supplies the payment condition, but with hundreds of price siblings including buy_crypto_price, it never says when to pick this per-token endpoint over the general one, nor any when-not condition. Usage is inferable rather than stated.

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