Skip to main content
Glama

recall_approval_request

Recalls pending approval requests for a record by cancelling approver rows, withdrawing approvals when they are no longer needed.

Instructions

Recall/withdraw approval requests on a record by cancelling pending approver rows (state → cancelled/no_longer_required). Requires WRITE_ENABLED=true

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": {
      "record": "<record>"
    },
    "name": "recall_approval_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordYessys_id of the record whose approvals to recall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true; the description adds real value beyond that by disclosing exactly what is mutated (pending approver rows) and the resulting states (cancelled / no_longer_required), plus the WRITE_ENABLED requirement. It does not say what happens to rows that are already decided, which is the main remaining ambiguity.

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?

One sentence, front-loaded with the action and scope, with the state-transition parenthetical and the write-flag prerequisite appended compactly. No filler or restated name/title content.

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 one-parameter mutation with annotations present and no output schema, the description covers action, target, effect and a prerequisite. It is slightly short on outcome detail (e.g. whether the count of recalled approvals is returned), but that is a minor gap.

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 ('sys_id of the record whose approvals to recall'), so the schema already carries the semantics. The description's phrase 'on a record' reinforces but does not extend that, 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?

The description gives a specific verb pair (recall/withdraw) plus the resource (approval requests on a record) and even the mechanism (cancelling pending approver rows). It is clearly distinct from approve_request/reject_request style siblings by naming the withdrawal action, though it never names an alternative tool 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?

Usage is implied by the verb: use this to pull back approvals that are still pending. The WRITE_ENABLED=true prerequisite is a useful gating condition, but there is no explicit when-not guidance (e.g. what to do for already-decided approvals) and no named alternative for related operations such as reject_request.

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