Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MOVE

Paid. Movement (MOVE) 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/MOVE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 meaningful work: it discloses this is a paid call, the exact price and payment rails, that no auth/account is required, and that failed calls are not charged. It stops short of stating data freshness, rate limits, or what a success/failure response 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?

Six short clauses, front-loaded with the paid flag and the payload, then cost, then access terms, then the endpoint. Nothing is redundant and the payment details are not buried.

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 parameterless paid price lookup with no output schema, the description covers cost, payment chains, auth requirements and returned fields, which is essentially everything needed to decide and call. Only freshness/update cadence and response shape are absent.

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; the description correctly adds nothing about inputs and instead specifies the asset is fixed by the endpoint URL, which prevents an agent from hunting for a symbol argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (Movement / MOVE) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. It also labels the tool as 'Paid', which separates it from the free read-style siblings in a catalog of hundreds of near-identical per-asset tools.

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 commercial terms ($0.01 USDC on Base or Solana, no account/key, failed calls not charged) imply 'use this when you want this one asset's price and are willing to pay', but there is no explicit routing advice against obvious alternatives such as buy_coin_MOVE, buy_crypto_price or buy_tok_* variants. The agent must infer which of several MOVE-related tools to call.

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