Skip to main content
Glama
Sign In

AlphAI

by io.github.makeev
OverviewDiscussionsAdmin

Unsubscribe from ticker alerts

alphai_alerts_unsubscribe
DestructiveIdempotent

WRITE operation (deactivates a saved subscription in the caller's account). Soft-disable the caller's news-alert subscription for the given ticker. Idempotent — returns {removed: false} if the alert was already inactive. Raises unknown_ticker for an unrecognized symbol. OAuth connections need the alerts.write scope (raises insufficient_scope otherwise); API keys have it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "alphai_alerts_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker to unsubscribe from.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / maxLength
      Added value: +16
    • addedInput schema / properties / ticker / pattern
      Added value: +"^[A-Za-z0-9.\\-]+$"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value on top: it clarifies the operation is a soft-disable rather than a hard delete, gives the concrete idempotent return shape {removed: false}, and spells out the required alerts.write scope for OAuth vs API keys. This is meaningful behavioral context that annotations alone do not convey.

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?

Four short sentences, front-loaded with the operation type and effect, followed by idempotency, errors, and auth. Every sentence carries distinct information with no 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 one-parameter mutation with an output schema, this covers everything an agent needs: effect, idempotency, failure modes, and auth requirements. Return values need not be explained since an output schema exists, yet the description still flags the key branch.

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% and the single ticker parameter is fully documented with a pattern and maxLength in the schema. The description only restates 'for the given ticker' and adds no format or edge-case detail beyond what the schema provides, so the baseline 3 applies.

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 and resource: soft-disables the caller's news-alert subscription for a given ticker. It is immediately distinguishable from the sibling alphai_alerts_subscribe, and the 'WRITE operation' prefix frames the operation type up front.

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?

Clearly scoped to the caller's own account and to an existing subscription, with the errors (unknown_ticker, insufficient_scope) telling the agent what preconditions matter. It does not explicitly name the subscribe sibling as the inverse action, so routing guidance is implied rather than stated.

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

All AlphAI toolsInspect
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.

Resources