Skip to main content
Glama

Get an action

get_action
Read-only

Follows an asynchronous action (create, reinstall, power…). Poll until status leaves running; on error it carries the reason. Scope: vms.read.

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": {
      "action": "<action>"
    },
    "name": "get_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction id, as returned by create_vm, power_vm, reinstall_vm or list_vm_actions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / action / description
      Added value: +"Action id, as returned by create_vm, power_vm, reinstall_vm or list_vm_actions."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it read-only and open-world; the description adds meaningful behavior beyond that: asynchronous polling, exit condition when status leaves running, and that errors carry a reason. It does not cover polling cadence, timeout behavior, or detailed return fields.

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, front-loaded with the core behavior and polling exit condition, then the scope. There is no redundant wording.

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 simple one-parameter asynchronous-action poller with no output schema, the description gives the essential operational context: what it follows, when polling stops, and how errors are surfaced. Minor gaps like poll interval or timeout are not critical at this complexity.

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 coverage is 100%, and the schema itself documents the single action parameter as an ID returned by create_vm, power_vm, reinstall_vm, or list_vm_actions. The description adds usage context but no additional meaning beyond what the schema already provides.

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: following an asynchronous action, with examples (create, reinstall, power) and the polling condition. This clearly distinguishes it from sibling operations like create_vm or get_vm.

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?

Explains when to use it by saying to poll until status leaves running and notes that action IDs come from create_vm, power_vm, reinstall_vm, or list_vm_actions. It lacks explicit when-not-to-use guidance or named alternatives, but the context is clear.

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.