Skip to main content
Glama
Sign In
Prufa

Prufa

Official
by prufa-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

prufa_list_monitor_deliveries

Retrieve the last 50 deploy-hook deliveries for a monitor, including ready-to-use CI snippets for curl, GitHub Actions, and GitLab CI. Surface never-fired webhook events to identify integration issues.

Instructions

List a monitor's last 50 deploy-hook deliveries plus copy-paste CI snippets (curl, github_actions, gitlab_ci). never_fired:true powers the 'your webhook never fired' nudge — surface it to the human. [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_list_monitor_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.6/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 the behavioral disclosure burden. It reveals a 50-delivery limit and explains the never_fired flag, but does not disclose read-only nature, authorization needs, or any 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no filler. The main action is front-loaded, and the second sentence adds essential context about the never_fired flag.

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?

No output schema exists, so the description should clarify the return format. It mentions a list of deliveries and CI snippets, but omits fields, ordering, or pagination. Adequate but not complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the parameter. It implies 'monitor_id' identifies the monitor, but does not specify format, source, or other details. This is minimal compensation.

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 tool lists a monitor's last 50 deploy-hook deliveries and provides CI snippets. The mention of 'never_fired:true' adds specific behavior. It distinguishes from sibling tools like prufa_list_monitors by focusing on deliveries.

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 the tool should be used when needing delivery history or CI snippets, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives.

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