Skip to main content
Glama

SouthPow crypto & market data

buy_tok_INTCX

Paid. Intel xStock (INTCX) 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/INTCX.

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

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 well: it discloses that the call is paid, the exact cost and accepted chains, that no account or API key is needed, and that failed calls are not charged. It could be even stronger with rate-limit or data-freshness details, but the key payment and failure semantics are covered.

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?

The description is front-loaded with the paid nature and the returned data, followed by cost, access requirements, and failure policy. It is efficient overall, though 'price: live USD price' is slightly redundant and the URL could be integrated more cleanly.

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 no-parameter paid API with no output schema, the description is nearly complete: it names the returned fields, price, payment chains, authentication requirements, and failure charging policy. It does not describe the response format or payment flow (e.g., x402), which keeps it from a 5.

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 has zero parameters, so there is no parameter semantics to clarify. The description does not need to compensate for missing schema documentation; baseline 4 applies.

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 clearly identifies the resource—Intel xStock (INTCX)—and the specific data returned: live USD price, 24h change, and market-cap rank. It lacks an explicit verb like 'get' or 'fetch,' but the purpose is still unambiguous and distinguishable from sibling token-price tools by the INTCX ticker.

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 implied by the ticker and returned fields, and the description mentions it is paid. However, it does not state when to choose this over nearby siblings such as buy_tok_INTCB or buy_crypto_price, nor does it mention prerequisites beyond the payment details.

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