delete_scan
Delete a saved scan by name.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | the name of the saved scan to delete |
PatternsRadar — NSE stock screener
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/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 of behavioral disclosure. It names the destructive action but does not disclose permanence, whether the scan must exist, failure behavior, or side effects. The word 'Delete' conveys only the most basic behavioral trait.
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?
The description is a single concise sentence that is front-loaded with the core action and resource. There is no redundant or filler content.
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 minimal one-parameter delete tool, this is adequate but not rich. With no annotations and no output schema, the description is the only behavioral context; it could usefully mention that deletion is permanent or how missing scans are handled.
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 description coverage is 100%, so the baseline is 3. The description's 'by name' merely restates the schema's name parameter without adding new semantic detail.
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 uses a specific verb ('Delete') with a clear resource ('a saved scan') and the method ('by name'). It clearly distinguishes this tool from siblings like save_scan, run_scan, and list_saved_scans.
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?
No explicit guidance on when to use this tool versus alternatives is provided. The purpose is obvious because only this sibling performs deletion, so usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool targets a clearly distinct action: symbol discovery, symbol metadata, price bars, query reference, scan execution, saved scan management, market metadata, and historical replay. run_scan and hitrate are differentiated as current matches versus past performance, so there is no meaningful overlap.
Naming Consistency4/5
Most tool names follow a lowercase snake_case verb_noun pattern such as delete_scan, get_bars, run_scan, save_scan, and search_symbols. A few names like hitrate, market_meta, and sift_reference break that pattern but remain consistent in style and readable.
Tool Count5/5
Ten tools is well-scoped for an NSE stock screener. Each tool earns its place and together they cover symbol lookup, market data, querying, saved scan lifecycle, and historical evaluation without redundancy.
Completeness4/5
The core screener workflow is covered: find symbols, fetch bars and metadata, learn the query language, run scans, manage saved scans, and evaluate hit rates. Minor gaps exist, such as no dedicated view for a single saved scan's full query and get_bars only returning recent bars, but these are workable limitations.