Skip to main content
Glama

Signal consensus batch

rayana_ai_signals
Read-only

Latest aggregator-consensus batch for one asset lane: which tickers cleared the signal pipeline, blended agg_score, confirming source count.

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

Input Schema

NameRequiredDescriptionDefault
laneNoAsset lane to read.equity
limitNoRows to return, from 1 to 200.

Output Schema

NameRequiredDescriptionDefault
laneYes
countYes
signalsYes
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lane / description
      Added value: +"Asset lane to read."
    • addedInput schema / properties / limit / description
      Added value: +"Rows to return, from 1 to 200."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes the recency framing ('latest') and the idea that rows are filtered by having 'cleared the signal pipeline', but says nothing about freshness windows, ordering, or how the batch is assembled — and 'openWorld' implies external data whose timeliness matters here.

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?

A single front-loaded sentence with no filler; the scope constraint comes first and the payload description second. Terms like 'agg_score' and 'signal pipeline' are mildly jargon-laden but compact rather than padded.

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?

An output schema exists, so the return-field explanation in the description is partly redundant and needn't be expanded. However, for a tool sitting alongside a similarly named consensus sibling, the definition leaves an agent without enough to decide which to call or what 'consensus' and 'cleared the pipeline' operationally mean.

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 the lane enum and limit range fully documented in the schema itself, so the baseline is 3. The description's 'for one asset lane' reinforces the lane parameter but adds no semantics for limit or ordering beyond what the schema states.

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 verb+resource: the latest aggregator-consensus batch for a single asset lane, and previews the payload (tickers that cleared the pipeline, blended agg_score, confirming source count). It does not differentiate itself from the sibling rayana_ai_consensus, so it stops short of a 5.

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 explicit when-to-use statement, no exclusions, and no named alternative. The presence of two consensus-flavored siblings (rayana_ai_signals vs rayana_ai_consensus) makes the absence of routing guidance a real gap; usage is only inferable from the phrase 'latest aggregator-consensus batch'.

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