Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

create_alert

Create a price alert that fires when price crosses a set level in TradingView, validating direction against live price and confirming the stored level.

Instructions

Create a price alert that fires when price crosses a level. Refuses a level on the wrong side of live price, and reads the alert back to confirm the stored level.

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": {
      "level": "<level>",
      "direction": "<direction>",
      "message": "<message>"
    },
    "name": "create_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
messageYes
directionYes
days_to_expireNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does meaningful work: it discloses a validation rule (a level on the wrong side of live price is refused) and a post-write verification step (the alert is read back to confirm the stored level). That tells the agent to expect a possible rejection on side-of-price grounds and that the tool performs a read after writing. It omits auth/permission requirements and duplicate-handling behavior, which keeps it from a 5.

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?

Two tight sentences, zero filler, with the core purpose front-loaded before the behavioral caveats. Every clause earns its place by adding either scope or behavior.

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 mutation tool with no annotations, no output schema, and 0% parameter documentation, the description covers the important behavioral risk (side-of-price rejection) and hints at the return path via the read-back. It is still incomplete on parameter meanings, the failure mode's exact error shape, and whether the returned alert is the sole response.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must compensate and largely does not. It gives meaning to level and indirectly to direction (crossing up or down), but message and days_to_expire (bounded 1-60) are never mentioned, leaving the agent to guess at the notification text field and the expiry semantics.

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 names a specific verb and resource ("Create a price alert") plus its trigger condition ("fires when price crosses a level"), which clearly separates it from modify_alert, delete_alert, and list_alerts without needing to name them. It stops short of explicitly contrasting with modify_alert, but the create-vs-modify distinction is unambiguous from the verb.

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?

Usage is implied rather than stated: the description tells you this creates a new alert, so an agent can infer it should not be used to change or remove an existing one. There is no explicit when-to-use/when-not-to-use guidance, no mention of what to do if an alert already exists for that level, and no routing to modify_alert or list_alerts as alternatives.

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