Skip to main content
Glama

actions-update

Destructive

Update an action

Update the settings of an action: its name, type, queues and values. The new settings apply the next time the action is executed. Updating an action does not execute it.

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": {
      "request": "<request>"
    },
    "name": "actions-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds useful behavior beyond that: the change is deferred until the next execution and the action is not run. It stops short of explaining what makes the call destructive or whether the body is a partial patch or a full replacement of fields such as possibleValues and filterInQueueIds.

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 short sentences, front-loaded with the action and immediately followed by the deferred-effect caveat. The opening line partially duplicates the first sentence, which is minor waste rather than bloat.

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 destructive mutation with a nested request object and no output schema, the description covers the timing behavior but leaves two agent-critical questions open: whether omitted body fields are cleared or left untouched, and whether updating possibleValues replaces the existing value set. Those gaps keep it at minimum-viable rather than complete.

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?

Reported schema coverage is 0%, so the description must compensate, and it does so partially by naming four of the mutable fields (name, type, queues, values). The nested schema does carry inline descriptions for the remaining fields (key, builtIn, freeText, position, valueRequired, queueBehaviour) and for projectId, which limits how much more the description needed to say.

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 ("Update the settings of an action") and enumerates the mutable surface: name, type, queues and values. It also explicitly distinguishes itself from actions-execute by asserting the update does not trigger execution, so an agent can route between the two without opening sibling schemas.

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?

The description clarifies timing (new settings take effect at the next execution) and rules out an execution side effect, which is genuine usage context. However, it gives no explicit when-to-use-vs-alternatives guidance against actions-create or actions-delete, and no prerequisites or permission requirements are stated.

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