Skip to main content
Glama

sentiment

Read-onlyIdempotent

Analyze sentiment of text in crypto, finance, social media, or general context. Returns score (-1 to 1), confidence, label (very_bearish to very_bullish), reasoning, and per-entity sentiment. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "text": "<text>"
    },
    "name": "sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to analyze for sentiment
contextNoContext for sentiment analysiscrypto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description correctly spends its words elsewhere: it discloses a 10-calls-per-day free quota and the x402 pay-per-call fallback with pricing. It does not say what auth or wallet setup the paid path requires, nor how oversized or invalid text is handled, which keeps it short of 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?

Two sentences with no filler: capability and domains first, then return shape, then the quota constraint. Every clause carries information the agent needs.

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?

With no output schema present, the description steps in to name the return fields (score, confidence, label range, reasoning, per-entity sentiment), which is the key gap it needed to close. Remaining omissions are minor: no error behavior for oversized text and no detail on the paid path's mechanics.

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 description coverage is 100% with both parameters documented and the context enum fully enumerated in the schema. The description restates the same context values without adding syntax, format, or selection guidance beyond them, so the baseline 3 applies.

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 ('Analyze sentiment of text') plus the domain scoping ('crypto, finance, social media, or general context'). This is unmistakably distinct from the other text-handling siblings (summarize, translate) and an agent can select it 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 Guidelines3/5

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

The enumeration of contexts implies when each mode applies, and the free-tier/quota sentence tells the agent to budget calls. However, there is no explicit when-to-use vs. when-not guidance and no naming of alternatives such as summarize for neutral condensation versus sentiment scoring.

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.