Skip to main content
Glama

test_trigger

Test the trigger's working copy on recent real records, run every playbook's filter on them, and compare with the live version. Required before publish_trigger, and it counts only for exactly this working copy. Reads only: nothing is queued and nothing runs. The result keeps counts and problems, never the records. madeUpRecords are extra records you write (shaped like the app's) to check that filters survive missing fields; they never count as a pass. Use when validating fetch/filter behaviour before going live.

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

Input Schema

NameRequiredDescriptionDefault
triggerIdYesThe trigger's id, from list_triggers or create_trigger.
madeUpRecordsNoUp to 20 made-up records, each { recordKey, record }.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial context beyond annotations: nothing is queued and nothing runs, results retain only counts and problems (never the records), and madeUpRecords never count as a pass. The one gap is that 'Reads only' sits in mild tension with readOnlyHint=false; the description could reconcile why the annotation marks it non-read-only (live external fetches, possible stored test result).

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?

Front-loaded with what it does, then the publish_trigger prerequisite, then the read-only and result-shape caveats, then the madeUpRecords nuance. Every sentence carries distinct information and none repeat the schema.

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

Completeness5/5

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

For a two-parameter tool with no output schema, the description covers what is compared, what is not mutated, what the result contains, and the edge case of synthetic records. An agent has enough to call it correctly and interpret the response.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines triggerId and the madeUpRecords shape. The description still earns credit by explaining why madeUpRecords exist (checking filters survive missing fields) and the non-obvious rule that they never count as a pass — semantics the schema cannot express.

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?

States a specific verb and resource chain: test the trigger's working copy against recent real records, run every playbook's filter, and diff against the live version. This is clearly distinguishable from siblings like get_trigger (inspection) and publish_trigger (promotion), and the working-copy scope is stated up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says it is required before publish_trigger, that the result only counts for exactly this working copy, and to use it when validating fetch/filter behaviour before going live. The when-to-use and the gating relationship to a named sibling are both spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources