Skip to main content
Glama

All's Well

Get monitor

get-monitor
Read-only

Get one monitor by id, including status, SSL info, 30-day uptime, whether it is still proving itself, and its alert contacts.

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": {
      "id": "<id>"
    },
    "name": "get-monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe monitor id (from list-monitors).
reveal_heartbeat_urlNoSet true only when you need to give the heartbeat URL to a job you are setting up. The URL is a secret: anyone with it can report the job as healthy. Don't print or store it anywhere else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reveal_heartbeat_url
      Added value: +{
      +  "default": false,
      +  "description": "Set true only when you need to give the heartbeat URL to a job you are setting up. The URL is a secret: anyone with it can report the job as healthy. Don't print or store it anywhere else.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description usefully discloses what the response includes and hints at the transient 'proving itself' state, but says nothing about the secret nature of the heartbeat URL or any cost/rate characteristics of a detail fetch.

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 no filler; the fetch scope comes first and the returned data follows immediately. Nothing here could be cut without losing information.

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?

With no output schema, the description must carry the return-shape burden, and it does so reasonably by naming the main fields returned. It is slightly thin on the sensitive heartbeat-URL reveal path, though the schema covers that adequately.

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% and the schema already explains both parameters thoroughly, including the secret-handling warning on reveal_heartbeat_url, so baseline 3 applies. The description adds a small amount by tying the lookup to the id and framing the returned fields, but adds no syntax or format detail beyond 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 ('Get one monitor by id') and enumerates the payload an agent can expect: status, SSL info, 30-day uptime, proving-self state, and alert contacts. The singular 'one monitor by id' cleanly separates it from list-monitors without needing to name it.

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

Usage Guidelines3/5

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

Usage is implied by 'by id' and the id parameter note '(from list-monitors)', so an agent can infer the list-then-fetch flow. But there is no explicit when-to-use or when-not statement, and no alternative (e.g. list-monitors for browsing) is called out in the description itself.

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