AlphAI

Subscribe to ticker alerts

alphai_alerts_subscribe

DestructiveIdempotent

WRITE operation (creates/updates a saved subscription in the caller's account). Subscribe the caller to ticker news alerts. Optional category_filter (e.g. ['earnings','insider']) restricts which categories trigger; min_relevance_score raises the threshold. This is a partial update: omitting either field on an existing subscription preserves its current value, and a brand-new subscription defaults min_relevance_score to 7. Note the threshold applies to email and telegram delivery; a Pro webhook receives the full matched stream and filters on its own. Raises tier_not_paid / unknown_ticker / limit_reached. Crypto alerts use the -USD ticker (BTC-USD); subscribing to a collider string like BTC binds the stock/ETF that owns it and the response's note field says so.

Input Schema

TableJSON Schema

Name	Required	Description
`ticker`	Yes	Ticker to subscribe to (active symbol).
`category_filter`	No	Categories that trigger alerts.
`min_relevance_score`	No	Min relevance to alert on.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`ticker`	Yes
`is_active`	Yes
`created_at`	Yes
`delivery_mode`	Yes
`category_filter`	No
`min_relevance_score`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026
- addedInput schema / properties / ticker / maxLength
```
Added value: +16
```
- addedInput schema / properties / ticker / pattern
```
Added value: +"^[A-Za-z0-9.\\-]+$"
```

Changed1 schema field changedSep 6, 2026

addedOutput schema / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedJun 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: documents partial-update semantics, the default threshold of 7, that the threshold governs email/telegram delivery while a Pro webhook receives the full stream, and enumerates domain error codes (tier_not_paid / unknown_ticker / limit_reached). Consistent with destructiveHint/idempotentHint and adds substantial, non-duplicative behavioral context.

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?

Front-loads the WRITE marker and core purpose, then layers semantics, errors, and edge cases. Dense but almost every clause carries distinct information; slightly long for a 3-parameter tool but not padded.

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?

Covers the mutation contract, defaults, delivery-channel nuance, error conditions, and ticker-format edge cases. With an output schema present, return values need not be explained, and the description leaves no material gap for correct invocation.

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?

Despite 100% schema coverage, the description adds real meaning beyond the schema: an example category_filter value, the behavioral default of 7 for min_relevance_score (schema lists default null), the <SYM>-USD crypto ticker convention, and the collider-string binding caveat surfaced in the response note field.

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 a specific verb+resource ('Subscribe the caller to ticker news alerts') and flags it as a WRITE operation that creates/updates a saved subscription. Clearly distinguishable from siblings like alphai_alerts_list and alphai_alerts_unsubscribe.

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?

Explains the partial-update contract and when each field matters (omitting preserves existing value; new subscription defaults min_relevance_score to 7), which implies usage context well. It does not explicitly name the alternate sibling tools (alerts_unsubscribe/alerts_list) as routing alternatives, so it falls short of a 5.

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.