Skip to main content
Glama
Sign In
signaldaemon-mcp

signaldaemon-mcp

by bevanding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_market_narratives

Read-only

Retrieve top crypto market narratives with strength, momentum, and price divergence signals, relative to a market snapshot of regime, 7d performance, and fear/greed index.

Instructions

Return top crypto market narratives with strength, momentum, and price divergence signals. Includes a market_snapshot (regime, market_7d, fear_greed) that every divergence reading is relative to.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds value by detailing the output components (narratives with strength, momentum, divergence, and market_snapshot) and notes that divergence readings are relative to the snapshot. However, it does not clarify data recency or how results change over time.

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?

The description is two sentences, front-loaded with the main purpose, and contains no extraneous information. It is concise and well-structured.

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 simple tool with one optional parameter and no output schema, the description adequately explains the return value. It could be more complete by explaining how to interpret strength/momentum scales or the effect of the limit parameter.

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

Parameters1/5

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

The description does not mention the only parameter 'limit' at all. With 0% schema description coverage, the description should compensate but fails to explain the parameter's purpose, default, or usage.

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?

The description clearly states it returns 'top crypto market narratives with strength, momentum, and price divergence signals' and includes a 'market_snapshot'. This is specific and distinguishes from the sibling tool 'get_clean_feed', which likely serves a different purpose.

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 description implies usage for fetching market narratives and signals, but does not explicitly state when to use this tool versus the sibling 'get_clean_feed' or provide any conditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools