Skip to main content
Glama

actions-retrieve

Read-only

Get an action

Get an action by ID: its type, where it shows in the review queues, the values it takes and its webhooks.

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-retrieve"
  }
}

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?

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful substance by naming the parts of the response the agent will receive, which matters because there is no output schema. It does not address the project/org-key scoping rules or missing-record behavior.

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 verb and resource, with the return contents immediately following. The only redundancy is restating "Get an action" before the colon, a minor cost.

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 single-parameter read-only retrieval tool with annotations and no output schema, the description covers what an agent needs: what it fetches and what comes back. The remaining gaps (scoping failures, not-found behavior) are handled by the schema text.

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?

The description contributes nothing about the parameters, but the visible schema already documents both `id` and the nontrivial `projectId` rules (org key vs. project key, cross-project access being an error) in detail. Given the reported 0% coverage metric, the description arguably should have compensated, but the effective documentation is strong enough that a 3 is fair rather than a 2.

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?

The description uses a specific verb (Get) and resource (an action) and enumerates what the returned action contains: its type, review-queue placement, values, and webhooks. That clearly separates it from actions-list, actions-create, and actions-update without naming them. It stops short of an explicit sibling callout, so it is not 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?

Usage is only implied by "by ID", which signals a single-record lookup as opposed to the list variant. There is no statement of when to prefer actions-list, what happens if the ID is unknown, or any prerequisite about project scoping.

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