Skip to main content
Glama

Stop monitoring

revoke_monitoring
DestructiveIdempotent

Stop further paid checks under this permission and pause the alert if it is the current one. Work already sent can finish and is charged. Works even while new monitoring is switched off.

Permission: monitoring:manage.

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": {
      "monitoring_id": "<monitoring_id>"
    },
    "name": "revoke_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitoring_idYesThe monitoring ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, but the description goes further by disclosing that in-flight work completes and is still charged, that an alert is paused only if it is the current one, and that the required permission is monitoring:manage. This is meaningful behavioral context beyond the structured fields; only the response shape is left to the output schema.

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?

Four short sentences, none wasted: the core action and its side effect are front-loaded, followed by the billing caveat, the edge-case enablement note, and the permission line. No repetition of the title or schema.

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 single-parameter mutation with a rich annotation set and an existing output schema, the description covers the important unknowns: partial-work billing, alert pausing behavior, and authorization. It is nearly complete, with only minor ambiguity about what happens to a paused alert afterward.

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% and the single monitoring_id parameter is already documented as 'the monitoring ID returned when it was quoted or created.' The description adds no syntax, format, or sourcing detail beyond the schema, so the baseline 3 applies.

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+resource pair: stop further paid checks under this monitoring permission and pause the associated alert. It is distinguishable from sibling verbs like cancel_check or get_monitoring because it names the monitoring scope and the billing consequence, though it never explicitly names an alternative tool for contrast.

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?

Implied usage is clear (call this to halt future paid checks on a monitoring), and 'Works even while new monitoring is switched off' gives a useful edge-case context. However, there is no explicit when-to-use vs. when-to-use-something-else guidance, nor any statement about preconditions other than the permission.

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.

Resources