Skip to main content
Glama

Sentiment signals

muhabbit_sentiment_signals
Read-only

Momentum, volume-weighted, regime and vertical-shift sentiment signals, across all verticals. (Needs an API key or wallet token: X-API-Key or Authorization: Bearer.)

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": "muhabbit_sentiment_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / vertical
      Removed value: -{
      -  "enum": [
      -    "crypto",
      -    "finance",
      -    "tech"
      -  ],
      -  "type": "string"
      -}
  2. Changed1 schema field changed
    • changedInput schema / properties / vertical / enum
      Previous value: -[
      -  "crypto",
      -  "finance",
      -  "tech",
      -  "turkish"
      -]New value: +[
      +  "crypto",
      +  "finance",
      +  "tech"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful non-schema context: the authentication requirement (X-API-Key or Bearer token) and that results span all verticals rather than a single scope. It says nothing about freshness, pagination, or response shape, so it adds context but not rich behavioral detail.

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 short sentences, front-loaded with what the tool returns and followed by the auth prerequisite. No filler, no restatement of the title.

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

Completeness3/5

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

Auth and scope are covered, and with no output schema the description is not obliged to document return values. However, the four signal types are dense jargon offered with no hint of how they differ or what an agent would do with them, and there is no routing vs sibling tools - a real gap for a zero-param call whose entire selection decision rests on the description.

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 clarify about inputs. The absence of parameters also means the description does not need to compensate for any schema coverage gap.

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?

Names a specific resource family - momentum, volume-weighted, regime and vertical-shift sentiment signals - and states its scope as 'across all verticals'. The verb ('retrieve') is implied rather than stated, and it never differentiates itself from siblings like muhabbit_asset_sentiment or muhabbit_sentiment_index, which is the gap keeping it at 4.

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?

There is no when-to-use or when-not-to-use guidance at all. With three sentiment-related siblings (asset_sentiment, sentiment_index, narrative_history) an agent has no basis in the description for choosing this tool over them - 'across all verticals' hints at breadth but never states the contrast.

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