Skip to main content
Glama

Read a pending action

get_pending_action
Read-onlyIdempotent

Read one pending action. The answer includes its state and outcome, without result rows. Open human_link to confirm or reject. This tool does not decide the action.

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": {
      "pending_action_id": "<pending_action_id>"
    },
    "name": "get_pending_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
pending_action_idYesUUID of the pending action

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is low. The description still adds real value by describing the payload shape (state and outcome) and by stating that result rows are excluded, which the annotations cannot convey. No contradiction with the declared hints.

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?

Four short sentences, front-loaded with the verb and the returned data, with no filler. The opening sentence largely restates the title, a minor redundancy in an otherwise efficient definition.

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 tool with full annotation coverage, the description covers purpose, payload, and the human hand-off. Without an output schema, naming the fields returned (state, outcome, absence of result rows) is the key missing piece it does supply; only sibling routing is absent.

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?

Only one parameter, and its schema description ("UUID of the pending action") plus 100% coverage already documents it fully. The description adds no format or sourcing detail beyond what the schema provides, so the baseline 3 applies.

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 ("Read one pending action") and specifies what the response contains: state and outcome, without result rows. It is distinguishable from a list operation, though it never names list_pending_actions or cancel_pending_action explicitly.

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?

Gives a concrete follow-up path ("Open human_link to confirm or reject") and disclaims agency ("does not decide the action"), which implies the human-in-the-loop workflow. However, it offers no explicit guidance on when to choose this over list_pending_actions or cancel_pending_action.

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