Pushary

Cancel Pending Question

cancel_question

DestructiveIdempotent

Retract a pending question that is no longer needed or is moving to the current client. Returns cancelled:true only when a pending question was removed. False may mean it was already answered, expired, missing or unavailable. An unavailable state includes handoffAction:stop because cancellation could not safely inspect or fence the question. Does not retract an answer already recorded.

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.1/5.0

Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), and the description usefully extends this by explaining what cancelled:false means (already answered, expired, missing, unavailable) and the handoffAction:stop edge case. This adds real behavioral context about failure modes, though some of it overlaps with the output schema.

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?

The core action and its scope are front-loaded in the first sentence, followed by tightly packed return semantics. Four sentences with little waste, though the return-value detail is dense relative to a two-parameter tool.

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 mutation tool, the description, annotations, and output schema together cover purpose, safety, and result interpretation. It could still say more about interaction with wait_for_answer, but nothing essential to correct invocation 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 coverage is 100%, so both parameters are already documented, including a detailed handoff description. The prose only echoes the 'moving to the current client' rationale for handoff and adds no syntax or format detail beyond the schema; baseline 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?

States a specific verb and resource ('Retract a pending question') plus the scope ('no longer needed or is moving to the current client'). It is clearly distinguishable from siblings like ask_user and wait_for_answer without opening a schema.

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?

Gives clear conditions for use ('no longer needed', 'moving to the current client') and one exclusion ('Does not retract an answer already recorded'). It stops short of naming sibling alternatives or an explicit not-use case against wait_for_answer, so it is strong but not fully routing.

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

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?