Skip to main content
Glama
Sign In
Pubrio

Pubrio

Official
by pubrio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reveal_monitor_signature

Retrieve the webhook signature secret for a monitor to verify webhook deliveries.

Instructions

Reveal the webhook signature secret for a monitor (for verifying webhook deliveries)

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": "reveal_monitor_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitor_idYesMonitor UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5
  2. Removed
  3. First observedv1.0.2

TDQS

B3.3/5.0
Behavior2/5

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

No behavioral traits beyond the action 'reveal' are disclosed. There is no mention of permissions required, side effects, or whether the secret is rotated. Since no annotations exist, the description carries the full burden but falls short.

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?

Single sentence, directly to the point, no redundant words. Front-loaded with the action and resource.

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?

The description covers the basic functionality but omits return value information (no output schema). For a simple tool, it is adequate but not fully complete.

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 coverage is 100% and the description does not add any new meaning beyond the schema's 'Monitor UUID' description. Baseline score of 3 is appropriate.

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 action 'Reveal' and the resource 'webhook signature secret for a monitor', with a parenthetical clarifying the purpose. It effectively distinguishes from sibling tools that handle monitor CRUD or other operations.

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?

No guidance on when to use this tool versus alternatives. The context of verifying webhook deliveries is implied but not explicit, and no exclusions or alternative tools 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