Skip to main content
Glama

Import monitors

import_monitors
Idempotent

Creates the monitors the user chose from preview_monitor_import (send their monitor objects). Each takes a plan slot like create_monitor; ones already monitored are skipped. Imported heartbeats get new URLs, returned once as heartbeat_url: tell the user to point their scheduled jobs at them. 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": {
      "monitors": "<monitors>"
    },
    "name": "import_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoThe preview's source, recorded in the audit log.
monitorsYesThe `monitor` objects of the preview's items to create, unchanged or edited (name, interval_seconds, status). Each takes a plan slot as a single new monitor would; one already monitored is skipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context the annotations cannot express: monitors consume plan slots, already-monitored items are skipped, and imported heartbeats get new one-time URLs the user must be told about. It also states the write-token requirement and that the import is free, which the readOnly/openWorld/destructive hints do not cover.

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-loads the action and the preview dependency, then layers in skip behavior, heartbeat URL warning, auth, and cost in four tight sentences. A few fragments ("Free.") are terse enough to be mildly ambiguous, but nothing is padded.

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?

With no output schema, the description still tells the agent the one return value that matters (heartbeat_url) and that it is shown only once. Combined with the plan-slot, skip, and auth notes, an agent has everything needed to call this correctly and relay results to the user.

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 both parameters are already documented in the schema, including the enum for source and the minItems/maxItems bounds. The description restates that monitor objects come from the preview but adds no new syntax or constraint information, 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?

Opens with a specific verb and resource ("Creates the monitors the user chose from preview_monitor_import") and pins down the input provenance, which a sibling like create_monitor would not have. An agent can immediately tell this is the bulk-commit half of a preview/commit pair.

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 routes the agent through preview_monitor_import first and explains the relationship to create_monitor (each monitor takes a plan slot). It stops short of an explicit "do not use for single ad-hoc monitors", but the sequencing and skip semantics imply it clearly.

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