Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BRIDGE

Paid. HyBridge (BRIDGE) 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/BRIDGE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on cost, accepted payment rails (USDC on Base or Solana), no account/API key, and the important 'failed calls not charged' clause, but says nothing about response shape, latency, or whether repeated calls are billed per invocation.

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 decisive fact ('Paid.') then flows cost, output fields, payment rails, auth, billing policy, endpoint URL in a compact fragment list. Every sentence earns its place and nothing is padded.

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-param paid data fetch with no output schema, the description covers the essentials an agent needs before committing money: what it returns, what it costs, how to pay, and that failures are free. The one remaining gap is return format/structure, which the field list only partially implies.

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 description to disambiguate; baseline 4 applies. The description correctly makes clear the asset and timeframe are baked into the endpoint rather than passed in.

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?

States precisely what is returned — live USD price, 24h change and market-cap rank — for a named asset (HyBridge / BRIDGE), which cleanly separates it from the hundreds of other buy_tok_* and buy_coin_* siblings. It never names a sibling it overlaps with (e.g. buy_crypto_price or the buy_cp_* category tools), so differentiation is by resource name only.

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?

The pricing and payment conditions implicitly say 'use only when you're willing to pay $0.01', but there is no explicit when-to-use or when-not-to-use guidance versus the free/alternative price tools in the sibling set. An agent must infer that a general crypto price lookup elsewhere may be cheaper.

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