Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

modify_alert

Change an existing TradingView alert's message or level in place by alert ID; level updates require a direction, and the alert is read back to confirm.

Instructions

Change an alert's message and/or level in place (same id). Changing the level needs direction. Reads it back to confirm.

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_id": "<alert_id>"
    },
    "name": "modify_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
messageNo
alert_idYes
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the whole burden. It does disclose useful traits: the mutation preserves the id, level changes require a direction, and the tool reads the alert back to confirm the change. It omits what happens on an unknown id, whether changes are reversible, and what the read-back actually returns.

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?

Three tight clauses, front-loaded with the core action, then the conditional rule, then the confirmation behavior. Every clause conveys information that is not duplicated elsewhere.

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 four-parameter mutation tool with no annotations and no output schema, the description covers the essential calling semantics but leaves error behavior, permission requirements, and the nature of the read-back result unaddressed.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate and largely does: "message and/or level" marks both as optional, "same id" identifies alert_id as the key, and "changing the level needs direction" supplies the conditional requirement the schema leaves ambiguous (only alert_id is listed as required). It doesn't explain what up/down means relative to the current numeric level.

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?

States a specific verb and resource (change an alert) plus the exact fields affected (message and/or level) and that it mutates in place under the same id, which implicitly separates it from create_alert and delete_alert. It does not name a sibling explicitly, so it falls just 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 Guidelines3/5

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

"In place (same id)" implies this is the tool for editing an existing alert rather than creating or deleting one, but there is no explicit when-to-use or when-not-to-use statement and no mention of prerequisites such as the alert existing or being owned by the caller.

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