Delete one of your monitors
delete_monitorDestructiveIdempotent
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Monitor id from list_monitors |
Starwell: World Data & Statistics
by dev.starwell
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
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
B3.4/5.0
Disambiguation5/5
Each tool targets a distinct operation: Q&A, deep analysis, series metadata, observations, stats, catalog search, and monitor CRUD. The only potential overlap between answer and deep_analysis is explicitly disambiguated by use-case guidance, and delete_monitor is unambiguous by name even without a description.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (get_*, list_*, create_*, delete_*, search_*). However, 'answer' and 'deep_analysis' deviate from this pattern, making the naming convention slightly inconsistent.
Tool Count5/5
With 11 tools, the server is well-scoped for a world data/statistics domain. It covers discovery, retrieval, analysis, and monitoring without unnecessary bloat, and each tool earns its place in the set.
Completeness5/5
The toolset provides a complete workflow: discover sources/datasets via list_sources/list_datasets/search_catalog, retrieve series/observations/stats via get_*, analyze via answer/deep_analysis, and manage monitors via create/list/delete_monitor. No critical operations are missing for the stated purpose.