Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

remove_drawing

Removes a single drawing from the open TradingView chart by its ID, letting you clear a specific annotation without affecting other drawings.

Instructions

Remove one drawing by id.

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": {
      "id": "<id>"
    },
    "name": "remove_drawing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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?

No annotations are provided, so the description carries the full behavioral burden, yet it only says "remove" and does not mention that deletion is irreversible, what happens if the id is unknown, whether permissions are required, or what the response looks like. "Remove" does at least convey a destructive operation and "by id" identifies the target, but that is all.

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?

One short, front-loaded sentence with no redundant wording. Its efficiency comes partly from under-specification rather than tight editing, but there is nothing wasted.

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 one-parameter deletion tool with no output schema and no annotations, the description is close to minimally viable. It lacks the destructive-undo caveat and error behavior that an agent would want before calling a delete operation.

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 0% and there is no type description in the schema, but the description's "by id" clarifies that the single parameter identifies the drawing to delete. That adds some meaning, though it doesn't specify where ids come from (e.g., list_drawings) or how to handle stale ids.

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?

"Remove one drawing by id" states a specific verb (remove) and resource (drawing), and the word "one" signals single-item scope, which implicitly separates it from a bulk-clear tool. However, it never names a sibling such as clear_drawings, so the distinction has to be inferred from the plural form of the sibling names.

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 explicit guidance on when to use this instead of clear_drawings or other drawing tools. The only hint is the word "one," leaving the agent to infer that clear_drawings handles bulk removal.

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