Skip to main content
Glama

Crypto sentiment

crypto_sentiment
Read-only

Aggregate social sentiment for any crypto token or topic. Returns an overall 0-100 bullish score, per-source breakdown (market, community, social), mention volume, and confidence level. Sources: Alternative.me Fear & Greed (market), CoinGecko community votes, and StockGeist social media analysis (when STOCKGEIST_API_KEY is configured). Costs $0.005 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "crypto_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken symbol, name, or topic (e.g. 'BTC', 'solana', 'ethereum')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover read-only and open-world nature, but the description adds genuinely non-obvious behavior: a metered cost of $0.005 USDC per call and conditional source availability (StockGeist only when STOCKGEIST_API_KEY is configured). It stops short of saying how the score degrades or what confidence means when a source is missing.

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?

Three sentences, front-loaded with purpose, then return values, then sources and cost. Every clause carries information an agent would otherwise have to infer; nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return fields (score scale, per-source breakdown, mention volume, confidence). For a single-parameter read tool, cost and source-availability notes close the remaining gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with an example-bearing description, so the schema already carries parameter meaning. The description's 'any crypto token or topic' only restates the accepted flexibility, adding no format, normalization, or resolution guidance beyond the schema.

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 verb and resource ('Aggregate social sentiment') plus the exact scope ('any crypto token or topic') and enumerates the output shape. It is clearly distinguishable from siblings like fear_greed_index or prediction_market_sentiment because those are named inputs here rather than the product.

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 'any crypto token or topic' and by naming the constituent sources. It never says when to pick this over fear_greed_index (which it partially wraps) or prediction_market_sentiment, nor when a token-level sentiment read is preferable to a price or risk tool.

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