Skip to main content
Glama

Novig market data (novigapi.com)

delete_watchlists

Delete one of your Watchlists. Cannot be undone, so confirm with your user first.

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>",
      "user_request": "<user_request>"
    },
    "name": "delete_watchlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
user_requestYesThe current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 burden and does disclose the single most important trait: the deletion cannot be undone. It also flags the confirmation step, which is real behavioral guidance. It stops short of stating permission requirements or what happens to any dependent data, so it is not exhaustive.

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 short sentences, both front-loaded and load-bearing: the first states what it does, the second states the risk and the required precaution. No filler whatsoever.

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 destructive, annotation-free tool it covers the essential risk disclosure and confirmation requirement, but leaves an agent unsure where a valid id comes from and what the call returns. It is adequate but has a clear missing piece given the absence of annotations and output schema.

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 only 50%: user_request is documented in the schema, but id has no description anywhere. The description implies id identifies the watchlist but adds no format, source, or origin information (e.g., that ids come from list_watchlists), so it fails to compensate for the coverage gap.

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 ("Delete one of your Watchlists"), which cleanly separates it from the create/get/list/update watchlist siblings even though none are named. The scope is unambiguous and requires no schema inspection to understand.

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?

Provides an implicit usage rule – confirm with the user before calling – which is genuinely actionable for an irreversible action. It does not, however, say when deletion is appropriate versus alternatives (e.g., updating a watchlist instead) or point to list_watchlists as the way to obtain a valid id.

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.