Skip to main content
Glama
Sign In
Prufa

Prufa

Official
by prufa-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prufa_get_monitor

Fetch configuration and live state of a monitor—status, cadence, last run, and deploy-hook metadata—to track its health.

Instructions

Get one monitor's config + latest state (status, cadence, last run, deploy-hook metadata). [Pro]

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": {
      "monitor_id": "<monitor_id>"
    },
    "name": "prufa_get_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that it returns config and state fields, and the '[Pro]' tag suggests a plan requirement. However, it does not describe error behavior (e.g., missing monitor), permission needs, or side effects.

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?

The description is a single sentence that front-loads the core purpose. It is concise, but could benefit from additional structure (e.g., separating config and state). No superfluous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (1 param, no output schema, no nested objects), the description provides fundamental details. However, it lacks explanation of output format, error cases, or usage context, leaving the agent to guess about return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter (monitor_id) with 0% description coverage. The description adds no context about what monitor_id is, where to get it, or its format. For a tool with low schema coverage, the description must compensate but fails to do so.

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

Purpose5/5

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

The description clearly states the verb 'Get', the resource 'one monitor', and specifies what is returned: 'config + latest state (status, cadence, last run, deploy-hook metadata)'. This distinguishes it from sibling tools like prufa_list_monitors (listing all) and mutation tools.

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 description implies usage for retrieving a single monitor's details but provides no explicit guidance on when to use this vs. alternatives (e.g., list_monitors) or when not to use it. No prerequisites or exclusions are mentioned.

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