Skip to main content
Glama
Sign In
exit1-mcp

exit1-mcp

by Mopra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Enable or disable check

toggle_check
Idempotent

Pause or resume an uptime check without deleting it. Disabling stops probing and alerting; enabling resumes monitoring.

Instructions

Enable or disable a check without deleting it. Disabled checks stop probing and stop alerting — use this rather than delete_check for a temporary pause.

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": {
      "check_id": "<check_id>",
      "disabled": "<disabled>"
    },
    "name": "toggle_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYesThe check ID returned by list_checks or create_check
disabledYestrue to pause the check, false to resume it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false; the description adds genuinely new behavioral context by explaining the functional consequence of the flag ('stop probing and stop alerting'), which an agent cannot infer from the annotations alone. It stops short of stating reversibility or persistence of the disabled state.

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 sentences, front-loaded with the action and scope, then the routing advice. Zero filler and nothing redundant with the title.

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 2-parameter toggle with no output schema, the description covers purpose, effect, and the sibling alternative. Only minor gaps remain, such as whether the state persists or how it interacts with update_check.

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 schema already spells out both parameters, including the true/false meaning of 'disabled' and where check_id comes from. The description adds no syntax or format detail beyond that, 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?

States a specific verb pair (enable/disable) on a specific resource (check) and immediately scopes it as non-destructive, which distinguishes it from delete_check and update_check in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative and the selecting condition: 'use this rather than delete_check for a temporary pause.' It does not address the toggle vs. update_check boundary, but the when-to-use guidance is clear and actionable.

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

Deploy Server

Other Tools