Skip to main content
Glama

Preview importing monitors

preview_monitor_import
Read-only

Reads the monitors of another service: UptimeRobot (a read-only API key, or its bulk upload CSV), Better Stack (a team-based API token), Uptime Kuma (its JSON backup) or a CSV file in UpHeron's format (https://upheron.com/docs/import). Creates nothing: says which would be created and which skipped and why (no UpHeron check for it, already monitored, beyond the plan's monitors, needs Pro), with the UpHeron monitor each maps to. Show the user the list before import_monitors. The key is used once and never stored. Needs a write token. 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": {
      "source": "<source>"
    },
    "name": "preview_monitor_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoThe export file's text: a CSV for csv and uptimerobot, the backup JSON for uptime_kuma. At most 5 MB and 1,000 monitors.
sourceYesWhere the monitors come from: better_stack (API token), csv (UpHeron's CSV format or UptimeRobot's bulk upload template), uptime_kuma (the JSON backup of Uptime Kuma 1.x) or uptimerobot (read-only API key, or its bulk upload CSV).
api_keyNoFor uptimerobot, a read-only API key (UptimeRobot: Integrations → API); for better_stack, a team-based API token (Better Stack: API tokens → Team-based tokens). Used once to list the monitors, never stored or logged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial context beyond readOnlyHint/openWorldHint: enumerates the exact skip reasons (no UpHeron check, already monitored, beyond plan, needs Pro), states the credential is used once and never stored or logged, and notes a write token is required. The auth-token requirement for a read-only operation is genuinely useful information the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and tightly packed, but the long parenthetical source list and the enumerated skip reasons make it dense and slightly run-on. Every clause does carry information, so nothing is wasted, though it could be split for readability.

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

Completeness5/5

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

Covers sources, credential handling, the shape of the result (which monitors would be created, which skipped, and why, plus the mapped UpHeron monitor), and the required next step. With no output schema, this prose fully compensates for what is missing structurally.

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 is 3; the description nevertheless adds the source-to-parameter mapping (UptimeRobot takes a read-only key or its bulk CSV, Better Stack a team token, Kuma a JSON backup), which helps the agent pick the right combination. It stops short of repeating format details already present in the schema.

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 and resource ('Reads the monitors of another service') and enumerates the four supported sources. It is clearly a dry-run preview rather than the actual import, which separates it from the sibling import_monitors.

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

Usage Guidelines5/5

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

Explicitly prescribes the workflow: 'Show the user the list before import_monitors', naming the alternative tool and the condition that selects it. It also states the negative case ('Creates nothing') so the agent knows this is a safe pre-step.

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