Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-fear-greed

Fear Greed: Crypto market sentiment: Fear-and-Greed index (0-100) with classification from alternative.me. 🆓 5 free trial calls per signed wallet

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": "x402-fear-greed"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the upstream source (alternative.me), the output scale and classification, and an access constraint ('5 free trial calls per signed wallet') implying wallet signing is required. It does not state rate limits, freshness/cadence of the index, or failure behavior, leaving meaningful gaps for a paid endpoint.

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?

Two compact clauses, front-loaded with the index name and meaning, followed by the source and trial terms. The emoji and repeated colon construction are minor noise but nothing is wasted or buried.

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 data lookup with no output schema, the description supplies the value range, classification, and data source — enough to call and interpret it. Only the refresh cadence and exact response fields remain unspecified, which is a modest gap.

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 mention of a signed wallet is access metadata rather than a call parameter.

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 the specific resource: the crypto Fear-and-Greed index on a 0-100 scale with classification, sourced from alternative.me. An agent can immediately tell this returns market sentiment rather than prices or news, though the phrasing is a noun label rather than an explicit verb.

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

Usage Guidelines2/5

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

No guidance on when to call this versus siblings such as x402-market-pulse, x402-crypto-trending, or the similarly named x402-publish-...fear--greed-index tool. The only contextual cue is the trial-call note, which speaks to billing, not usage.

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.