AlphAI

Subscribe to ticker alerts

alphai_alerts_subscribe

Idempotent

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.8/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behaviors: partial updates preserve omitted fields on existing subscriptions, new subscriptions default min_relevance_score to 7, thresholds apply to email/telegram but not Pro webhooks, exact error conditions are listed, and crypto tickers require the -USD suffix to avoid colliders. This is rich behavioral context that annotations alone could never provide.

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 dense but every sentence earns its place: operation type, parameter behavior, update semantics, delivery-channel nuance, error list, and crypto edge case. It is front-loaded with the core purpose and then layers necessary caveats without redundancy.

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 subscription tool with partial-update semantics and special cases, the description covers all the non-obvious behavior an agent needs: default values, delivery-channel differences, error conditions, and the crypto ticker format. The output schema exists, so the description needn't explain the return structure, and it even references the response's note field for the collider case.

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?

Even though schema description coverage is 100%, the description adds significant meaning: it gives an example category_filter value, explains that min_relevance_score raises the threshold, clarifies the default value for new subscriptions, and describes the ticker collider issue (BTC vs BTC-USD). This goes well beyond the schema's short field 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?

The description opens with 'WRITE operation (creates/updates a saved subscription in the caller's account)' and then states 'Subscribe the caller to ticker news alerts.' This gives a specific verb, resource, and side-effect, and clearly separates this from the sibling read tool alphai_alerts_list and deletion tool 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?

Clear context is provided: the tool is the write path for creating or updating a saved subscription, and the partial-update behavior tells an agent exactly how to modify an existing subscription. However, it never explicitly names alphai_alerts_list or alphai_alerts_unsubscribe as alternatives, so an agent must infer when to read or remove instead.

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.