Skip to main content
Glama
Sign In
exit1-mcp

exit1-mcp

by Mopra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get status page

get_status_page
Read-onlyIdempotent

Retrieve a public status page snapshot to view each check's current status and uptime percentage by providing its status page ID.

Instructions

Get the current snapshot of a public status page, with each check's status and uptime percentage.

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": {
      "status_page_id": "<status_page_id>"
    },
    "name": "get_status_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
status_page_idYesThe status page ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: this returns a point-in-time snapshot (no history) and includes per-check status and uptime percentage, which no structured field conveys.

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?

One sentence, front-loaded with the action and resource, with the return content trailing. Nothing is padded or repeated from the title.

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 tool with no output schema, the description covers both what it fetches and the shape of what comes back. It stops short of noting snapshot freshness/refresh semantics or how to obtain the status page ID, which would be the only remaining gaps.

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 at 100% schema description coverage, so the schema already documents status_page_id fully. The description adds no format, source, or lookup guidance for that ID, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get the current snapshot of a public status page') and even summarizes the payload ('each check's status and uptime percentage'). It does not explicitly name a sibling, but the resource is distinctive enough against the check/account/alert tools in the sibling list to be unambiguous.

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 the scope ('public status page' snapshot) but there is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_check or get_check_stats. An agent can infer intent but must guess at the boundary cases.

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

Deploy Server

Other Tools