Skip to main content
Glama

Set the uptime monitor

set_uptime_monitor
Idempotent

Set or replace the URL Fictura pings every minute (three failures in a row mark it down and alert). A new URL starts over as unknown. enabled false pauses it. Only works when the app allows MCP writes.

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": {
      "url": "<url>"
    },
    "name": "set_uptime_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) URL, like https://api.example.com/health
enabledNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses the check cadence (every minute), the failure threshold and alerting behavior (three failures in a row), the reset semantics of a new URL ("starts over as unknown"), and the write-permission gate. These are exactly the operational facts an agent cannot infer from readOnlyHint/idempotentHint/destructiveHint, and nothing contradicts them — replace semantics are consistent with idempotentHint=true and destructiveHint=false.

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, front-loaded with what the tool does, followed by reset and pause semantics and then the write-permission caveat. Every sentence contributes a distinct fact with 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 two-parameter setter with no output schema and full annotations, the description covers operation, alerting, reset, pause, and permission gating. It omits what a success response looks like and what happens on an invalid or unreachable URL, which are minor gaps but real ones.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema lacks: the URL is what gets pinged on a recurring schedule, and enabled=false specifically pauses rather than removes the monitor. That goes beyond the schema's terse "Default true".

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?

The description uses a specific verb pair ("Set or replace") and names the resource concretely: the URL Fictura pings every minute. It clearly contrasts with get_uptime_monitor by implication of set-vs-get, though it never names that sibling explicitly.

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?

It gives a real precondition — "Only works when the app allows MCP writes" — which tells the agent when the call will fail, and "enabled false pauses it" clarifies how to use the tool to disable monitoring rather than delete it. It stops short of explicitly routing to alternatives, but no exclusion is needed for a simple setter.

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