Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HINC

Paid. Neuberger Securitize High Income Tokenized Fund (HINC) 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/HINC.

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

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 at all, the description does real work: it discloses the paywalled nature, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — all material to an agent that must decide whether to spend. It does not describe latency, rate limits, or data freshness beyond 'live'.

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?

Two dense sentences, front-loaded with the paid flag and the resource, then payload, price, payment, and endpoint. Every clause carries actionable information and nothing is repeated from name or schema.

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, no-output-schema price lookup, the description covers what is returned, what it costs, how to pay, and where the endpoint lives. Only the exact response shape and update cadence are left unspecified, which is a minor gap for a tool this simple.

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 the baseline is 4. The description correctly conveys that the token is fixed (HINC in the endpoint path), so an agent knows no symbol or chain argument is required.

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?

States a specific resource (Neuberger Securitize High Income Tokenized Fund / HINC) and exactly what is returned: live USD price, 24h change, and market-cap rank. Among hundreds of buy_tok_* siblings, the token identifier plus the 'price' framing makes it clear this is the HINC price-feed tool rather than a data or yield tool.

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 (call this to get the HINC price) but there is no explicit when-to-use / when-not-to-use guidance, e.g. no routing versus buy_crypto_price or the buy_yields_protocol_* variants. The 'Paid' marker and cost line give practical context but not selection logic.

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