Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Stop watching a page

uptime_remove_monitor
DestructiveIdempotent

Remove a monitor and stop its monthly rent. Its history goes with it. Free.

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "uptime_remove_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitor_idYesThe monitor_id uptime_add_monitor returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint and idempotentHint, so the description's added value is the concrete consequences: history is deleted and billing ('monthly rent') stops, plus 'Free' clarifying no charge for removal itself. It does not say whether data can be recovered afterward, which is the one meaningful omission for a destructive tool.

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?

Three short sentences, zero padding, with the destructive consequence front-loaded right after the action.

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

Completeness4/5

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

For a one-parameter destructive tool with annotations and no output schema, the description covers action, data loss, and billing effect. Only the irreversibility/restore question is left open, which is a modest gap.

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 100% and the single monitor_id parameter is fully documented in the schema, including that it comes from uptime_add_monitor. The description adds nothing about the parameter, so baseline 3 applies.

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?

Names a specific verb (remove) and resource (monitor) plus the two consequences: rent stops and history is deleted. Clearly separable from uptime_add_monitor and uptime_update_monitor without opening a schema.

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?

The permanence implied by 'its history goes with it' suggests when removal is appropriate, but the description never states when NOT to use it — e.g. to pause monitoring temporarily, use uptime_update_monitor instead. No sibling is named.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources