Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STEAKCUSDC

Paid. Steakhouse Confidential Prime USDC (STEAKCUSDC) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/STEAKCUSDC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does well: it discloses the price, accepted payment assets and chains, absence of auth requirements, and the 'failed calls not charged' billing rule, which is the key risk an agent needs to know. It stops short of stating rate limits, whether charges occur per attempt versus per success in edge cases, or the response shape.

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?

Front-loads the payment status, then the resource and returned fields, then the operational facts (cost, rails, auth, billing) and the endpoint. Every clause carries distinct information with no filler.

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 covers cost, payment method, auth, failure billing, and the fields returned, which is nearly everything needed to call it. The remaining gap is response format and any rate limiting, which matters slightly more here because there is no output schema to fall back on.

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 nothing for the schema to document and no semantic gap to fill; baseline 4 applies. The description correctly adds no parameter talk, matching the parameterless contract.

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 resource (Steakhouse Confidential Prime USDC / STEAKCUSDC) and enumerates exactly what the call returns: live USD price, 24h change, and market-cap rank. An agent can tell which token this covers, though the 'buy_' verb itself is only implied by the leading 'Paid.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the practical preconditions for use: it is paid, costs $0.05 USDC on Base or Solana, and requires no account or API key, which tells an agent it can call this without setup. It does not discuss alternatives (e.g. free price sources or the adjacent buy_crypto_price / buy_yields_token_steakusdc tools), so routing between siblings is left to inference.

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