Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN44

Paid. Score (SN44) 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/SN44.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavioral burden and does substantial work: it declares the tool is paid, prices it at $0.01 USDC, lists accepted chains (Base or Solana), states no account or API key is needed, and confirms failed calls are not charged. It omits rate limits, latency, and response format, which keeps it from a 5.

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?

Six short fragments, front-loaded with the gating fact ("Paid.") before the payload, price, access terms, and endpoint. Nothing is padded. The phrase "Score (SN44) price" is slightly compressed to the point of ambiguity about whether 'Score' is the token name or a metric.

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, single-endpoint paid fetch with no output schema, the description covers what is returned, what it costs, how to pay, and that failures are free — enough to call it correctly. The absence of any return-shape hint is the main remaining gap, though the field list partially compensates.

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 input schema is empty, so there are no parameters whose meaning could be clarified; the baseline for zero-param tools applies. The description correctly adds no parameter text, and instead pins the subject (SN44) inside the description itself, which is the right place given nothing is passed at call time.

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?

The description names a concrete resource and enumerates the payload: "Score (SN44) price: live USD price, 24h change and market-cap rank." An agent can tell it returns quote data for a specific subnet token rather than an audit, TVL, or yield feed. It stops short of explicitly distinguishing itself from near-neighbors like buy_crypto_price or the buy_coin_* family.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, despite ~900 sibling buy_* tools including many other subnet tokens (SN14, SN19, SN24). The only selection signal is the token symbol embedded in the name and the description's opening line.

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