AlphAI

Stories (top or latest)

alphai_stories

Read-onlyIdempotent

Stories: market events that two or more publishers reported, each summarised by AlphAI from its articles. list=top (default) ranks the last 48 hours — importance (the feed's 1-10 scale, 7 and above) plus a coverage bonus, minus one point per 12 hours since the facts last changed, one slot per ticker — use it for 'what matters today'. list=latest pages every story newest-first by its latest article; follow next_cursor. Each card carries story_id, the summary's title and lead, importance, publishers, materials (articles) and summary_state (published / stale = new articles since the summary / preparing = no summary yet, texts are the lead article's). Call alphai_story with a story_id for the full summary — key facts with their sources, why it matters, the per-ticker read, open questions — and the articles behind it. Compared with alphai_trending, which ranks single articles, this ranks events and only those with independent coverage; most feed items are carried by one outlet and never become a story. Summaries are AI-generated financial information for research, not investment advice.

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

Input Schema

Name	Required	Description	Default
`list`	No	top = ranked last 48 hours (default); latest = newest-first, paginated.	top
`limit`	No	Stories per page, 1-50; default 10.
`cursor`	No	Opaque next_cursor from a latest page, unchanged.

Output Schema

Name	Required	Description	Default
`list`	Yes
`as_of`	No
`results`	Yes
`next_cursor`	No
`research_only`	No
`ranking_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent/non-destructive annotations, the description explains the ranking formula, the 48-hour window, pagination behavior, summary_state meanings, and that texts are the lead article's when no summary exists. It also discloses that summaries are AI-generated financial information for research rather than investment advice.

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?

The description is front-loaded with the core definition and then moves through modes, card fields, and sibling routing. It is dense but mostly earns its length given the tool's complexity; the long parenthetical ranking formula makes it slightly harder to scan than ideal.

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

Completeness5/5

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

The description covers the two listing modes, ranking logic, pagination, returned card fields, summary states, and the follow-up path to alphai_story. With an output schema and annotations present, this is complete enough for an agent to call the tool correctly.

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?

Schema coverage is 100%, so the enum and defaults are already documented. The description still adds useful semantic detail for list=top versus list=latest and explains that cursor is the next_cursor from a latest page, though it does not add much beyond the schema for limit.

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 states a specific verb and resource: it lists market-event stories that have independent publisher coverage. It distinguishes itself from alphai_trending, which ranks single articles, and from alphai_story, which retrieves a full summary by story_id. An agent can identify both what the tool returns and how it differs from its closest siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly says to use list=top for 'what matters today' and list=latest for newest-first pagination, including following next_cursor. It names alphai_story as the follow-up for full summaries and explains that alphai_trending ranks articles rather than independently covered events.

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

All AlphAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.