Skip to main content
Glama

Narratives

muhabbit_narratives
Read-only

Ranked live narrative clusters by phase, velocity and distinct-source count. Use for themes, rotations, or 'what's the story in crypto right now?' — returns decision-ready rows, not a raw feed. (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_narratives"
  }
}

Input Schema

NameRequiredDescriptionDefault
verticalNo
emerging_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / vertical / enum
      Previous value: -[
      -  "crypto",
      -  "finance",
      -  "tech",
      -  "turkish"
      -]New value: +[
      +  "crypto",
      +  "finance",
      +  "tech"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds genuinely useful context: the auth requirement (X-API-Key or Bearer token) and that output is 'decision-ready rows, not a raw feed.' However, it does not disclose ordering details, pagination/limits, or what fields a row contains, so the added behavioral depth is moderate rather than rich for a read tool with annotations already covering safety.

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 sentences, ranking metric front-loaded, use cases second, auth constraint tucked in a parenthetical. No filler, though the parenthetical could be its own clearly labeled note.

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, output character, and use cases are covered, and there is no output schema to explain. But with two undocumented optional parameters and no explanation of how vertical/emerging_only change results, an agent cannot fully reason about the call surface.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to carry parameter meaning and largely does not: 'vertical' and 'emerging_only' are never mentioned. 'By phase' hints at what emerging_only might filter, but neither the enum scope (crypto/finance/tech) nor the boolean's effect is clarified.

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 specific resource and ranking basis: 'Ranked live narrative clusters by phase, velocity and distinct-source count.' The word 'live' implicitly separates it from muhabbit_narrative_history, but no sibling is named explicitly, so differentiation is implied 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 Guidelines4/5

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

Gives concrete use cases ('themes, rotations, or what's the story in crypto right now?') and contrasts the output with a raw feed. It stops short of naming an alternative tool or an explicit when-not condition, which keeps it below a 5.

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