Skip to main content
Glama

SouthPow crypto & market data

buy_fng_now

Paid. Crypto Fear & Greed Index now (0 = extreme fear, 100 = extreme greed). $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/fear-greed.

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

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?

No annotations are supplied, so the description carries the full burden, and it discloses the things that matter most for an autonomous paid call: exact price, payment networks, no auth requirement, and that failed calls are not charged. It omits the payment mechanics (how the $0.01 is settled without parameters) and rate limits, but the economic and auth profile is unusually well 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?

Front-loads 'Paid.' then states resource, scale, cost, rails, and auth in compact clauses with no filler; the endpoint URL is the only element an agent arguably doesn't need. Slightly telegram-style, but every clause carries information.

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, one-value data purchase this covers cost, rails, auth, failure billing, and value semantics. The one remaining gap is the return shape (e.g., whether it returns a JSON object with value and timestamp) — with no output schema, the description should have said what comes back.

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; the 0-100 scale note is a bonus beyond schema scope. Baseline 4 applies for a parameterless tool.

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 a concrete verb+resource: buy/retrieve the Crypto Fear & Greed Index 'now', with the 0-100 scale defined inline so the agent knows what the value means. The word 'now' implicitly separates it from the buy_fng_7d / buy_fng_30d / buy_fng_90d siblings, but it never names them, so differentiation is inferred rather than stated.

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?

It gives useful preconditions ($0.01 USDC on Base or Solana, no account, no API key) that tell an agent whether it can call this at all. However, there is no explicit routing guidance — nothing says to use this for the current reading and buy_fng_7d/30d/90d for historical windows, which is the main selection decision an agent faces among these siblings.

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