Skip to main content
Glama
Sign In
Pubrio

Pubrio

Official
by pubrio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

test_run_monitor

Preview signal triggers by executing a test run of a monitor. Simulate a specific timestamp to evaluate expected outcomes before full activation.

Instructions

Execute a test run of a signal monitor to preview what it would trigger

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

Input Schema

NameRequiredDescriptionDefault
tried_atNoISO 8601 timestamp to simulate the run at
monitor_idYesMonitor UUID to test

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

States it is a test run and preview, indicating non-destructive behavior. With no annotations, this is adequate behavioral disclosure.

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 with no wasted words. Verb appears first, achieving front-loading.

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?

Adequately covers purpose and parameters. Lacks explicit mention of return value, but 'preview' implies output. Appropriate for a simple test tool.

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% so baseline is 3. Description adds only minor restatement of schema descriptions. No additional semantic value beyond schema.

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?

Description uses specific verb-resource combination: 'Execute a test run of a signal monitor'. It clearly distinguishes from sibling tools like create_monitor or retry_monitor.

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?

Implies usage for previewing triggers but provides no explicit when-to-use or when-not-to-use guidance, nor mentions alternatives like retry_monitor.

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