Skip to main content
Glama

test_trigger

Execute a trigger with a test payload to validate webhook or schedule behavior before relying on it; this runs the agent, consumes tokens, and may cause external side effects.

Instructions

Execute a trigger with a test payload. This runs the agent, consumes tokens and may cause external side effects.

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": {
      "trigger_id": "<trigger_id>"
    },
    "name": "test_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
trigger_idYesUUID of the trigger to test
test_payloadNoTest payload. For webhooks: {"chatInput":"Test message"}. For schedules, omit to use the scheduled query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.4
    • changedInput schema / properties / test_payload / description
      Previous value: -"Payload de teste. Para webhook: { \"chatInput\": \"mensagem teste\" }. Para schedule: omitir (usa query do cron)."New value: +"Test payload. For webhooks: {\"chatInput\":\"Test message\"}. For schedules, omit to use the scheduled query."
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger a testar"New value: +"UUID of the trigger to test"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds real context beyond the annotations: it warns that execution runs the agent, consumes tokens, and may cause external side effects. That cost-and-side-effect disclosure is meaningful given openWorldHint=true and destructiveHint=false. It stops short of saying whether the test run is logged in trigger execution history or how side effects can be avoided.

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 sentences, zero waste, with the action stated first and the cost/side-effect warning immediately after. Every sentence earns its place.

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?

For a two-parameter test-execution tool with no output schema, the description covers the essential risk profile an agent needs before invoking it. Minor gaps remain around whether test runs appear in execution logs and what permissions are required.

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%, and the schema itself explains the webhook versus schedule payload semantics, so the description needs to add little. It contributes nothing parameter-specific beyond what the schema already documents, which is the expected baseline.

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?

States a specific verb and resource: execute a trigger with a test payload. It is clearly distinguishable from test_mcp_server and from lifecycle siblings like create_trigger or toggle_trigger, though it does not explicitly name those alternatives.

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?

Usage is implied rather than stated: 'test payload' and 'test_trigger' suggest using this to try out a trigger before relying on it. There is no explicit when-to-use versus when-not guidance, no mention of prerequisites, and no pointer to siblings such as test_mcp_server.

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