Skip to main content
Glama

Get the uptime monitor

get_uptime_monitor
Read-only

The URL Fictura pings every minute for this app, whether it is up or down, the last check, consecutive failures, when the current downtime started, and availability over 24 hours and 7 days. monitor is null when none is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_uptime_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the payload contents and, crucially, the null-on-unconfigured behavior, but it says nothing about freshness of the check data, rate limits, or whether an unconfigured monitor can be distinguished from a monitor that is down.

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?

A single sentence with no filler, and the most useful context (which URL is pinged, at what cadence) is front-loaded ahead of the field enumeration. It reads as a run-on list rather than a structured summary, which slightly hurts scanability, but every clause carries 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 input parameters, no output schema, and strong annotations, the description is the only place return shape can be communicated — and it does that thoroughly, including the null case. The remaining gap is behavioral rather than informational: no note on data staleness or how a 'none set' state should be handled by the caller.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline applies. Nothing in the description is needed to explain inputs; the schema is trivially complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what data the tool surfaces (checked URL, up/down state, last check, consecutive failures, downtime start, 24h/7d availability), so the resource is clear, but it never states a verb — the agent has to infer 'get' from the name/title. It also does not distinguish itself from set_uptime_monitor, which is arguably the main confusion risk for a tool whose sibling writes the same object.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives; the closest thing is the precondition 'monitor is null when none is set', which tells the agent what an empty result means but not when to reach for this tool versus set_uptime_monitor or get_setup_status. Usage must be inferred entirely from the returned-field list.

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