Skip to main content
Glama

get_trigger

Read-onlyIdempotent

Get one trigger in full: its working copy (app, event, scope, fetch code), the playbooks that use it with their rules and filter code, its schedule and last check, and the result of its last test. It also gives definitionHash and lookBackTarget, which publish_trigger needs back. Use when inspecting a trigger or confirming what would go live before publish_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": {
      "triggerId": "<triggerId>"
    },
    "name": "get_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeZoneNoThe user's IANA time zone, e.g. "Australia/Sydney". Pass it when you know it: times are read back on the user's own clock and never in UTC. Without one, a time of day is refused and no clock times are shown.
triggerIdYesThe trigger's id, from list_triggers or create_trigger.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds value by disclosing the return payload's structure (working copy, playbooks, schedule, last test) and by flagging that `definitionHash` and `lookBackTarget` must be fed back into publish_trigger. That is genuine behavioral context an agent would otherwise have to discover by calling. It does not mention failure behavior for a missing trigger or payload size, so it is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two sentences, front-loaded with the payload contents and closing with the usage cue. The parenthetical enumeration is dense but every item is informative rather than filler. Minor cost: the long field list reads as a run-on and could be scanned faster as a short list.

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?

With no output schema, the description carries the return-shape burden and does so by naming the major sections of the response plus the two fields publish_trigger consumes. Combined with read-only annotations and fully documented parameters, an agent has enough to call it correctly. The only gap is error/not-found behavior, which is minor for a read 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 description coverage is 100%, and the timeZone parameter already carries a rich explanation in the schema, so the baseline is 3. The description adds no parameter-level meaning at all — it never mentions timeZone or the id-provenance rule, which the schema handles instead.

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 opens with a specific verb and resource ('Get one trigger in full') and then enumerates exactly what 'in full' means: working copy fields, attached playbooks with rules and filter code, schedule and last check, and last test result. That level of specificity lets an agent distinguish it from list_triggers (enumeration) and get_playbook (a different resource) without opening the schema.

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

Usage Guidelines4/5

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

It states two concrete situations: 'inspecting a trigger' and 'confirming what would go live before publish_trigger'. That is clear when-to-use guidance and ties the tool to a named sibling workflow. It stops short of explicit exclusions (e.g., use list_triggers first to find the id), which keeps it from a 5.

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