Skip to main content
Glama

Get monitor

get_monitor

Fetch a monitor's configuration summary by UUID, covering type, frequency, threshold, extractor, labels, and timestamps, to inspect its current setup.

Instructions

Get one monitor's configuration summary by uuid (type, frequency, threshold, extractor, labels, timestamps).

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": {
      "uuid": "<uuid>"
    },
    "name": "get_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does establish that this is a non-mutating single-record configuration read rather than a result/history read. It says nothing about error behavior for a bad or foreign uuid, permissions, or whether sensitive values (e.g. extractor credentials, webhook secrets) are masked in the response.

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?

A single front-loaded sentence with the identifying scope first and the returned fields parenthesized at the end; every element earns its place and nothing is padded.

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 one-parameter, read-only getter with no output schema, enumerating the returned fields is exactly the compensating detail needed. The only missing piece is what the description does not cover about failure modes or field masking, which is minor for a simple lookup.

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?

With one parameter at 100% schema coverage, the schema already documents uuid and its provenance ('from list_monitors'). The description restates that provenance rather than adding new meaning such as format expectations or behavior on an unknown uuid, so the 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?

The description names a specific verb and resource ('Get one monitor's configuration summary') and pins the lookup key ('by uuid'), so the agent can distinguish it from list_monitors or the result-oriented getters without opening the schema. It even enumerates what 'configuration summary' contains, removing ambiguity about the payload.

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 supplies a concrete prerequisite by noting the uuid comes 'from list_monitors', which tells the agent the natural entry path into this tool. It stops short of explicit exclusions such as pointing to get_latest_result when the agent actually wants run output rather than configuration.

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