confirm-mcp

Check a pending approval

check_approval

Poll an approval request by ID to check if a human has made a decision. Use the result to proceed or modify your next steps.

Instructions

Poll a previously created approval request by id to see if a human has decided yet.

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": {
      "id": "<id>"
    },
    "name": "check_approval"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The approval request id returned by request_approval.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It indicates a poll (read-oriented) operation and adds context about human decision, but it does not specify the return format, possible errors, or whether it is strictly non-mutating. For a simple tool, this is adequate but not rich.

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 a single sentence that immediately states the action and purpose. Every word contributes, with no filler or redundant information.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description covers the essential aspects: what it does, what it expects (id), and what it checks for. It lacks details about return values, but that is acceptable for a straightforward polling tool.

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 input schema already fully documents the 'id' parameter, including its source from request_approval. The description only says 'by id' and adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the action (poll), the resource (previously created approval request), and the purpose (see if a human has decided). It distinguishes from the sibling tool request_approval by focusing on checking an existing request rather than creating one.

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?

The description implies the tool is used after request_approval by saying 'previously created approval request'. It provides clear context for when to use it, though it does not explicitly state exclusions or mention alternatives beyond the sibling context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server