Skip to main content
Glama

Cancel approval

browser_cancel_approval

Withdraw a pending approval the agent requested. Required: sessionId, approvalId from APPROVAL_REQUIRED or APPROVAL_PENDING. The waiting command fails; this is not a human Deny. An expired approval returns APPROVAL_EXPIRED (recoverable) and is not cancelled. pendingApprovals on browser_get_status does not count that row.

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": {
      "sessionId": "<sessionId>",
      "approvalId": "<approvalId>"
    },
    "name": "browser_cancel_approval"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
approvalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: the waiting command fails, it is not a human Deny, expired approvals return APPROVAL_EXPIRED and remain uncancelled, and browser_get_status pendingApprovals does not count the row. These details clarify side effects and status semantics that annotations alone do not cover.

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?

The description is front-loaded with the core action, then adds required context, side effects, and edge cases in dense, relevant sentences. Every sentence contributes operational meaning without filler.

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 two-parameter cancellation tool with no output schema, the description covers key side effects and the expired-approval edge case well. It is slightly incomplete because it does not clarify the source of sessionId or describe the successful return behavior.

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 0%, so the description must carry parameter meaning. It gives the required parameter names and identifies approvalId as coming from APPROVAL_REQUIRED or APPROVAL_PENDING, but it does not explain where sessionId comes from or add format guidance.

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?

The description uses a specific verb and resource: withdraw a pending approval the agent requested. It also distinguishes the action from a human Deny and references browser_get_status, which helps separate it from related approval/status siblings.

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?

It clearly states when to use the tool and which IDs are required, including where approvalId comes from. It also explains that this is not a human Deny and that expired approvals are not cancelled, though it does not explicitly point to browser_get_approval for inspection.

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.