Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MWIN

Paid. Midas Wellington Income Opportunities (MWIN) 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/MWIN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 substantial work: paid, exact price ($0.01 USDC), accepted chains (Base or Solana), no account or API key required, and no charge for failed calls. It omits latency, rate limits and what the failure mode looks like, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is sold and what comes back, then price, payment rails, auth posture and billing behavior, then the endpoint. Every sentence is a distinct fact and none repeat structured fields.

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 tool, listing the three returned fields compensates reasonably for the missing output schema, and payment/auth/billing details complete the picture. Response shape and freshness are still left to inference, so it is not fully self-contained.

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 the baseline is 4 and there is nothing for the description to disambiguate. The token symbol is baked into the name rather than passed as an argument, and the description correctly avoids inventing any input options.

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 (MWIN, spelled out as Midas Wellington Income Opportunities) and exactly what is returned: live USD price, 24h change and market-cap rank. Against hundreds of sibling buy_tok_* tools, the token symbol in the name plus the descriptive expansion lets an agent match the right variant without opening the schema.

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

Usage Guidelines4/5

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

The token-specific framing implicitly scopes usage to MWIN quotes and the cost line tells the agent what it is committing to before calling. There is no explicit statement of when to prefer an alternative (e.g. buy_crypto_price for a broader quote) or any exclusion, so it stops short of full routing guidance.

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