Pushary

Cancel Pending Question

cancel_question

Idempotent

Retract a pending question so it can no longer be answered. Use this when a question became irrelevant before the user replied: the agent found the answer itself, the task was aborted, or a newer question supersedes it. Cancelling prevents a stale approval from arriving later and acting on work that has moved on. Only affects questions that are still pending; questions expire on their own 10 minutes after creation. Returns { cancelled: true } when a pending question was removed. False means it was already answered, expired, unknown, or unavailable; when status is unavailable, follow handoffAction and stop rather than opening another answer surface.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`handoff`	No	True when you are cancelling because you are about to ask the same question in the current client. For the next minute the Pushary hook then lets your own question tool through instead of sending it back to the phone. Set automatically whenever a live question is cancelled.
`correlationId`	Yes	The correlationId of the pending question to cancel, as returned by ask_user or send_notification

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	What to do when cancellation could not safely inspect the question.
`status`	No	Present when Pushary could not safely read or fence the question state.
`cancelled`	Yes	True when a still-pending question was removed. False when it was already terminal, missing, or unavailable; inspect status and handoffAction when present.
`askHandoff`	No	True when the session was marked as handing off to the current client, so the hook will not re-ask on the phone for the next minute.
`correlationId`	Yes	The question this result refers to, echoed back.
`handoffAction`	No	Stop rather than opening another answer surface when the question state is unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

addedInput schema / properties / handoff

Added value: +{
+  "description": "True when you are cancelling because you are about to ask the same question in the current client. For the next minute the Pushary hook then lets your own question tool through instead of sending it back to the phone. Set automatically whenever a live question is cancelled.",
+  "type": "boolean"
+}

addedOutput schema / properties / askHandoff

Added value: +{
+  "description": "True when the session was marked as handing off to the current client, so the hook will not re-ask on the phone for the next minute.",
+  "type": "boolean"
+}

Changed4 schema fields changedAug 24, 2026

changedOutput schema / properties / cancelled / description

Previous value: -"True when a still-pending question was removed. False when there was nothing to remove because it was already answered, already expired, or never existed."New value: +"True when a still-pending question was removed. False when it was already terminal, missing, or unavailable; inspect status and handoffAction when present."

addedOutput schema / properties / handoffAction

Added value: +{
+  "const": "stop",
+  "description": "Stop rather than opening another answer surface when the question state is unavailable.",
+  "type": "string"
+}

addedOutput schema / properties / hint

Added value: +{
+  "description": "What to do when cancellation could not safely inspect the question.",
+  "type": "string"
+}

addedOutput schema / properties / status

Added value: +{
+  "const": "unavailable",
+  "description": "Present when Pushary could not safely read or fence the question state.",
+  "type": "string"
+}

Changed1 schema field changedAug 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cancelled": {
+      "description": "True when a still-pending question was removed. False when there was nothing to remove because it was already answered, already expired, or never existed.",
+      "type": "boolean"
+    },
+    "correlationId": {
+      "description": "The question this result refers to, echoed back.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "cancelled",
+    "correlationId"
+  ],
+  "type": "object"
+}

First observedJul 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the idempotentHint annotation, the description discloses meaningful behavioral details: cancellation prevents stale approvals, only pending questions are affected, questions self-expire, and the return value semantics for true versus false are fully described, including the special unavailable status with handoffAction guidance.

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 dense but every sentence adds necessary context: action, use cases, rationale, scope limits, and return semantics. It is well-structured and front-loads the primary purpose before edge-case behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with an output schema, the description covers the full lifecycle: when to cancel, what happens after cancellation, what return values mean, and how to handle the unavailable status. Nothing needed to invoke or interpret the tool correctly is missing.

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 description coverage is 100%, so both parameters are already fully documented in the input schema. The description adds no new parameter-level meaning beyond what the schema provides, warranting the baseline score.

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 opens with a specific verb and resource: 'Retract a pending question so it can no longer be answered.' It immediately distinguishes itself from sibling tools like ask_user and wait_for_answer by focusing on cancellation of an already-issued question.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool — when the agent found the answer itself, the task was aborted, or a newer question supersedes it — and also states limits: only pending questions are affected, and questions expire after 10 minutes. This gives clear decision guidance without ambiguity.

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

All Pushary tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?