Skip to main content
Glama

SouthPow crypto & market data

buy_tok_JCT

Paid. Janction (JCT) 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/JCT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does a reasonable job: it discloses the $0.01 USDC cost, the two accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It omits rate limits, latency, and what a success response looks like, so it is informative but not rich.

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?

It is compact and front-loads the two decision-relevant facts: payment status ('Paid.') and the data returned. The cost, rail, and endpoint details follow as short fragments with no filler. The bare URL at the end is slightly raw but still earns its place as the call target.

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 lookup with no output schema, the description gives everything an agent needs to decide and pay: what data comes back, what it costs, on which chains, and that failures are free. Only response shape and freshness/polling expectations are left unstated.

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 and the schema is empty, so there is nothing for the description to disambiguate. The baseline of 4 applies – the description correctly implies the token is fixed by the tool identity rather than supplied 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 specific resource and what is returned: 'Janction (JCT) price: live USD price, 24h change and market-cap rank.' The ticker in the name is repeated in prose, so an agent can tell it apart from the surrounding buy_tok_* family. It never contrasts itself with the generic buy_crypto_price sibling, which is the only real ambiguity.

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. An agent can infer this is the JCT-specific paid price lookup, but the description gives no explicit 'use this when' rule, no exclusion, and no pointer to buy_crypto_price or buy_coin_* for alternative or bulk price needs.

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