Skip to main content
Glama

get_status

Read-only

The current status of a page: headline state, monitors, open incidents, planned maintenance, and the past 30 days against the uptime target.

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": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page id, from list_pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 value beyond that by disclosing the composition of the response — headline state, monitors, incidents, maintenance, and a 30-day window against an uptime target — which matters because there is no output schema. It does not mention data freshness or any rate limits, so it falls short of a 5.

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?

One compact sentence with zero filler, and the scope ('current status of a page') is front-loaded before the payload list. It is telegraphic rather than fully grammatical, but every clause earns its place by naming a returned section.

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 read-only, single-parameter tool with no output schema, the description covers both scope and expected return contents well enough to call correctly. The only gap is the absence of detail on freshness or whether the 30-day window is configurable, which is minor here.

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?

There is a single parameter, pageId, and the schema already documents it at 100% coverage, including the hint that it comes from list_pages. The description contributes nothing further about the parameter, which is acceptable given the schema does the work, but it adds no meaning of its own.

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?

The description names a specific resource (a page) and enumerates the exact payload: headline state, monitors, open incidents, planned maintenance, and 30-day uptime-vs-target. That enumeration makes it clearly distinct from siblings like get_dashboard or list_incidents without needing to name them. It lacks an explicit verb, reading as a noun phrase, which keeps it just short of a 5.

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 only implied by the phrase 'current status of a page' — an agent can infer this is the aggregate health view rather than a raw incident or monitor listing. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as list_incidents for detail vs. this tool for summary.

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