Skip to main content
Glama

get_trigger

Read-onlyIdempotent

Retrieve a trigger's current configuration by UUID so you can inspect or update it using accurate settings.

Instructions

Retrieve a trigger and its current configuration before inspection or update.

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

Input Schema

NameRequiredDescriptionDefault
trigger_idYesTrigger UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger"New value: +"Trigger UUID"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered without the description. The description contributes only the notion that the response includes the trigger's "current configuration", adding a little value but nothing on failure modes or permissions.

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?

One short sentence, front-loaded with the action and resource, with zero redundant wording. The trailing "before inspection or update" is slightly vague but earns its place as sequencing guidance.

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?

For a simple single-parameter read tool with complete annotations, most of what an agent needs is present. Since there is no output schema, the description should hint more about the returned shape, and "current configuration" is only a light indication.

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?

There is a single parameter with 100% schema description coverage ("Trigger UUID", format uuid), so the schema fully documents it. The description adds no format or lookup-context detail beyond that, making the baseline 3 appropriate.

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?

Specific verb (Retrieve) plus resource (a trigger and its current configuration), which is clearly distinct from mutation siblings like update_trigger or delete_trigger. It does not explicitly name a sibling to contrast against, so it stops short of a 5.

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?

"before inspection or update" implies this is a prerequisite read step prior to modifying a trigger, which is useful sequencing guidance. However, it never names the actual alternatives (e.g., update_trigger) or states when not to use this tool, so usage is only implied.

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