Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Turn alerts on or off

alert_set_status

Activate or deactivate Stockbit alerts by updating one or more alert IDs with an active or inactive status.

Instructions

Activates or deactivates alerts.

Endpoint: PATCH exodus /alert/v2/update-status.

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": {
      "alert_ids": "<alert_ids>",
      "status": "<status>"
    },
    "name": "alert_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status.
alert_idsYesAlert ids, from alert_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds only the raw endpoint string; it says nothing about whether a partially invalid id list fails the whole batch, whether re-setting an already-active alert is a no-op, or what the response contains.

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?

Two short lines with the purpose front-loaded and no filler. The endpoint line is of marginal value to an agent but is at least compact and clearly separated.

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

Completeness3/5

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

For a simple two-parameter mutation with no output schema, the purpose plus annotations plus fully described schema is minimally sufficient. The gaps are the batch semantics (up to 100 ids, partial failure behavior) and any indication of the returned result, which an agent would need to call this confidently at scale.

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% with enum values and the 'from alert_list' hint already documented per parameter. The description adds no interpretation of alert_ids or status, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb pair and resource ('Activates or deactivates alerts'), which is enough to distinguish it from siblings like alert_create and alert_delete. It lacks only an explicit contrast with those siblings, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alert_create/alert_delete, no prerequisite that alert ids must come from alert_list, and no mention that this operates on batches of up to 100 alerts. The only routing clue ('from alert_list') lives in the schema, not the description.

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

Deploy Server

Other Tools