Skip to main content
Glama

list_monitors

Read-only

The monitors on a page with their type, target, state and last result. archived true lists the archived ones instead.

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": {
      "pageId": "<pageId>"
    },
    "name": "list_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page id, from list_pages.
archivedNoList the archived monitors instead, latest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "List the archived monitors instead, latest first.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful nuance that archived=true swaps the result set rather than adding to it, but says nothing about volume limits, pagination, or ordering beyond what the schema states.

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?

Two short sentences with the resource and the key toggle front-loaded; nothing is wasted. It is telegraphic rather than well-formed prose ('The monitors on a page...'), which costs a point but not clarity.

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?

A simple read-only, two-parameter list tool with full schema coverage and no output schema. The description names the returned fields, which usefully stands in for a missing output schema, and covers the archived variant; only pagination/limit behavior is unaddressed.

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 description coverage is 100%, so both parameters are already documented, including pageId provenance and 'latest first' ordering. The description's 'archived true lists the archived ones instead' mostly restates the schema, adding only the exclusivity implication. Baseline 3 applies.

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?

Names a specific resource (monitors) scoped to a page (pageId, sourced from list_pages) and lists the fields returned (type, target, state, last result). It is not phrased as a verb phrase, and it doesn't distinguish itself from other listing tools beyond the resource name, but an agent can tell what it retrieves.

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?

The only usage guidance is the 'archived true' variant, which is implied rather than framed as when-to-use. There is no mention of prerequisites (a valid pageId), when to prefer a different listing tool, or what the default excludes — the agent must infer that omitting archived means non-archived monitors.

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