angelone-mcp

by pyalgobot

Overview Schema Source Related Servers Discussions Admin

Python

Remote

gtt_cancel_rule

Cancel an existing GTT rule by its ID, symbol token, and exchange to prevent it from executing.

Instructions

Cancel a GTT rule by its 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>",
      "symboltoken": "<symboltoken>",
      "exchange": "<exchange>"
    },
    "name": "gtt_cancel_rule"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`exchange`	Yes
`symboltoken`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 29, 2026

TDQS

B3.1/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 burden. 'Cancel' conveys mutation but nothing about side effects, idempotency, prerequisites, or error behavior.

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?

A single, direct sentence with no filler; the core action and key parameter are front-loaded.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the tool requires three parameters and only one is explained. Additional context about the role of symboltoken and exchange is needed for safe invocation.

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%, and the description only clarifies 'id'. The required 'symboltoken' and 'exchange' fields are left unexplained, so an agent cannot know what values to supply beyond their names.

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?

The description states a specific verb ('Cancel') and resource ('GTT rule') and identifies the primary key ('by its id'). It is clearly distinguishable from sibling tools like gtt_create_rule, gtt_modify_rule, and gtt_details.

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?

The description implies you should call this when you want to cancel a GTT rule and have its ID, but it gives no explicit when-to-use guidance or alternatives. It does not differentiate this from cancel_order or explain when gtt_modify_rule might be more appropriate.

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