Skip to main content
Glama

Hosted monitor status

monitor.status

Fetches the current QualityKit Cloud monitoring run when an API key is set; returns self-hosted/not-run coverage in free local mode.

Instructions

Fetch latest QualityKit Cloud monitoring run when QUALITYKIT_API_KEY is set. Otherwise returns self_hosted / not_run coverage (free local mode).

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": "monitor.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoPro API key (or set QUALITYKIT_API_KEY env)
apiBaseUrlNoQualityKit Cloud API base URL (or set QUALITYKIT_API_BASE). Required to call a hosted API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the conditional hosted/local behavior and the free local fallback, but it does not explicitly state read-only safety, failure behavior, or response characteristics beyond the fallback status.

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?

Two tightly written sentences with no wasted wording. The hosted behavior is front-loaded and the fallback is stated immediately afterward.

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?

The description covers both the hosted path and the local fallback, and the schema fully documents both optional parameters. For a simple status-read tool with no output schema, it is mostly complete, though failure modes and return details are not described.

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 the schema already documents apiKey and apiBaseUrl. The description mentions the API key environment variable but adds no further meaning about the parameters beyond what the schema provides.

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 states a specific verb and resource: fetching the latest QualityKit Cloud monitoring run. It also distinguishes the hosted path from the self-hosted/not_run fallback, though it does not compare itself to any sibling tool.

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?

It explains the condition that selects hosted mode versus local fallback, which gives implied guidance on when each behavior occurs. However, it does not explicitly say when to call this tool versus alternatives or mention any exclusions.

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