Skip to main content
Glama

SouthPow crypto & market data

buy_fng_30d

Paid. Crypto Fear & Greed Index, last 30 days with daily values and average. $0.005 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/fear-greed/30d.

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

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 burden and does a solid job: it discloses that the call is paid, the exact price ($0.005 USDC), the accepted chains (Base, Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining how payment is presented to the endpoint, whether the call is idempotent, or any rate limits.

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?

Front-loaded with 'Paid.' then purpose, then price/auth notes, then the endpoint URL — every sentence carries operational value. 'No account, no API key' is slightly redundant with 'No account', but overall the text is dense with no filler.

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 data endpoint with no output schema, the description covers cost, payment chains, auth requirements, failure charging policy, the endpoint, and the shape of the payload (daily values plus average). Only the concrete response fields and payment protocol details are left to discovery, which is acceptable here.

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; there is nothing for the description to disambiguate. The description correctly adds no parameter prose and instead spends its words on scope and cost.

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 (Crypto Fear & Greed Index) and a precise scope (last 30 days, daily values plus an average), which distinguishes it from buy_fng_7d, buy_fng_90d, and buy_fng_now by window. It does not explicitly call out those siblings, but the stated time window makes the choice unambiguous.

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 by the '30 days' window; there is no explicit statement of when to pick this over buy_fng_7d, buy_fng_90d, or buy_fng_now, nor advice such as 'use buy_fng_now for the current reading.' An agent can infer the routing but must do the work itself.

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