Skip to main content
Glama

AlphaAI

by io.github.makeev

Ticker news feed

alphai_ticker_news
Read-onlyIdempotent

Latest news for a single ticker (e.g. 'AAPL'). Cursor-paginated; returns the same shape (incl. the full inline AI analysis) as alphai_news_search. Insider news (SEC Form 4 insider trades) for the ticker is included by default — pass include_insider=false for a pure non-insider feed. min_relevance works exactly as in alphai_news_search (default 4, the full feed) — raise it to keep only what the enricher scored as material for this ticker. Set collapse_stories=true to get one row per story instead of every syndicated reprint. Sets unknown_ticker=true only for an unrecognized symbol string; a delisted symbol serves its history with delisted=true and renamed_to set when the company continues under a new ticker (querying the new ticker includes rows still tagged with the former one). Any share class of an issuer also serves rows tagged with its other listed classes (GOOGL includes rows tagged GOOG). Crypto is addressed as -USD (BTC-USD); a bare coin name nothing else owns resolves to it automatically, and when the bare string belongs to a stock/ETF instead (BTC is the Grayscale ETF), ticker_note names the coin ticker to request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNopublished (default): newest first. ingested: delta polling — only rows added since your cursor, ascending; next_cursor is always returned (empty items = caught up, keep the cursor and poll later). A cursor only works with the sort mode that issued it.
limitNoAlias for page_size.
cursorNoOpaque cursor from a prior next_cursor.
tickerYesTicker symbol, e.g. 'AAPL'.
page_sizeNoItems/page; capped at 20 Free/Basic, 50 Pro.
min_relevanceNoMinimum AI relevance score, 1-10.
include_insiderNoInclude SEC Form 4 insider news; default true.
collapse_storiesNoCollapse syndicated reprints to one representative per story and populate story_id/sources_count/sources (default false).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
itemsNo
delistedNo
renamed_toNo
next_cursorNo
ticker_noteNo
unknown_tickerNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changed
    • addedInput schema / properties / min_relevance
      Added value: +{
+  "default": 4,
+  "description": "Minimum AI relevance score, 1-10.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / page_size / description
      Previous value: -"Items/page; capped at 10 Basic / 50 Pro."New value: +"Items/page; capped at 20 Free/Basic, 50 Pro."
    • addedInput schema / properties / sort
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "published",
+        "ingested"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "published (default): newest first. ingested: delta polling — only rows added since your cursor, ascending; next_cursor is always returned (empty items = caught up, keep the cursor and poll later). A cursor only works with the sort mode that issued it."
+}
    • addedOutput schema / properties / delisted
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedOutput schema / properties / items / items / properties / created_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / items / items / properties / earnings
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / items / items / properties / insider
      Added value: +{
+  "anyOf": [
+    {
+      "description": "Structured SEC Form 4 event block (``alphai_insider_news`` items only).\n\nAggregate of the news row's whole transaction group — same semantics as the\nREST ``/api/news/insider/`` block (openapi.yaml: ``InsiderEvent``): shares and\nvalue are GROUP sums (a 10b5-1 ladder is one event), ``avg_price_usd`` is\nvalue-weighted over priced tranches, ``is_10b5_1`` is the group OR, the\nlast fill dates the event. ``side`` is the signal label: buy (P) / sell (S)\n/ other (everything else, incl. D — sale to issuer, a buyback/redemption,\nnot an open-market disposition); the raw ``transaction_code`` rides along.\nMoney/share fields are decimal STRINGS (\"25000\", \"187.32\") — flat, precise,\nschema-simple; null when the filing prices no tranche.\n\n``filed_at`` is when EDGAR accepted the filing and ``late_filing`` marks the\nones that missed the SEC's two-business-day deadline; the rule lives in\n``_is_late_filing`` in ``repository.py`` (ported from the backend's\n``apps.insider.services.filing_lateness``). Field reference for both\nsurfaces: ``backend/openapi.yaml`` (``InsiderEvent``).",
+      "properties": {
+        "avg_price_usd": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "filed_at": {
+          "type": "string"
+        },
+        "insider_name": {
+          "type": "string"
+        },
+        "insider_title": {
+          "type": "string"
+        },
+        "is_10b5_1": {
+          "type": "boolean"
+        },
+        "is_director": {
+          "type": "boolean"
+        },
+        "is_officer": {
+          "type": "boolean"
+        },
+        "is_ten_percent_owner": {
+          "type": "boolean"
+        },
+        "late_filing": {
+          "type": "boolean"
+        },
+        "shares": {
+          "type": "string"
+        },
+        "side": {
+          "type": "string"
+        },
+        "total_value_usd": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "transaction_code": {
+          "type": "string"
+        },
+        "transaction_date": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "side",
+        "transaction_code",
+        "shares",
+        "is_10b5_1",
+        "insider_name",
+        "insider_title",
+        "is_officer",
+        "is_director",
+        "is_ten_percent_owner",
+        "transaction_date",
+        "filed_at",
+        "late_filing"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / items / items / properties / source_type
      Added value: +{
+  "default": "",
+  "type": "string"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "uid",
-  "title",
-  "url",
-  "source",
-  "source_domain",
-  "summary",
-  "category",
-  "relevance_score",
-  "time_published"
-]New value: +[
+  "uid",
+  "title",
+  "url",
+  "source",
+  "source_domain",
+  "summary",
+  "category",
+  "relevance_score",
+  "time_published",
+  "created_at"
+]
    • addedOutput schema / properties / renamed_to
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / ticker_note
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 50,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias for page_size."
+}
    • changedInput schema / properties / page_size / description
      Previous value: -"Items/page. 10 Basic / 50 Pro (tools.bulk)."New value: +"Items/page; capped at 10 Basic / 50 Pro."
  3. Changed1 schema field changed
    • changedInput schema / properties / include_insider / description
      Previous value: -"Include insider/13F ownership news; default true."New value: +"Include SEC Form 4 insider news; default true."
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false; the description adds substantial behavioral context beyond that: cursor/pagination contract, unknown_ticker vs delisted with renamed_to semantics, share-class merging (GOOGL serves GOOG rows), crypto resolution including the bare-name rule and the BTC ETF ambiguity with ticker_note, and collapse_stories deduplication. No contradiction with the annotations.

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?

Dense but every clause carries information — the edge cases (delisted, renamed, GOOGL/GOOG, BTC) are all load-bearing for correct invocation, so the length is earned. It is front-loaded with the core purpose and pagination contract before edge cases, though the single wall of text would be easier to scan if broken into shorter grouped sentences.

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?

For a tool with 8 parameters and one required field, the description covers the full calling contract: pagination and cursor semantics, both sort modes, shape parity with alphai_news_search, and a thorough catalog of ticker edge cases. The output schema exists, so return values need no explanation. Nothing an agent needs to invoke this tool correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds meaning the schema lacks: min_relevance's default of 4 meaning the full feed and its materiality semantics, include_insider defaulting true and what a 'pure non-insider feed' means, collapse_stories' one-row-per-story effect, ticker's extensive formatting rules (SYM-USD, bare coin resolution, share classes, renamed tickers), and ingested-mode cursor behavior. This goes well beyond the schema's one-line property descriptions.

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?

States the specific function — 'Latest news for a single ticker' — with a concrete example ('AAPL'). It differentiates from the sibling alphai_news_search by noting it returns the same shape, and the single-ticker scope is unambiguous. The title is expanded with real substance rather than restated.

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?

The single-ticker scope makes the core use case clear, and repeated cross-references to alphai_news_search (same shape, same min_relevance semantics) help an agent map against its sibling. The sort modes give concrete when-to-use direction (published vs ingested for delta polling). However, it never explicitly says when not to use it or names alternatives like alphai_insider_news for insider-only queries, so it stops short of explicit exclusion guidance.

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

All AlphaAI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation3/5

Multiple news feed tools (alphai_actionable_now, alphai_trending, alphai_macro, alphai_ticker_news, alphai_news_search, alphai_insider_news, and search) overlap in purpose, so an agent could pick the wrong one by name alone. The detailed descriptions clarify each tool's window, scope, and filtering, but the set still relies heavily on reading those descriptions to avoid misselection.

Naming Consistency3/5

Most tools share the alphai_ prefix and snake_case, but there is no consistent verb_noun pattern: alphai_alerts_subscribe and alphai_news_search are verb phrases while alphai_ticker_news, alphai_macro, and alphai_calendar are noun phrases. The un-prefixed connector tools search and fetch add a further deviation, making the naming readable but mixed.

Tool Count3/5

At 16 tools, the set is at the heavy end and includes several near-duplicates: alphai_news_search vs search, alphai_article vs fetch, and alphai_insider_news vs alphai_news_search(category='insider'). The domain is broad enough to justify many specialized feeds, but the redundancies make it feel padded.

Completeness4/5

The toolset covers news discovery, search, article retrieval, alerts lifecycle, macro calendar, earnings reads, ticker metadata, and pair comparisons, so agents can complete most workflows. Minor gaps remain, such as no story-level detail endpoint and no broader user-account or watchlist management beyond alerts.

Resources