GetMattered

Cancel Applications

getmattered_cancel_applications

DestructiveIdempotent

Cancel queued or in-preparation applications before they are submitted, so nothing reaches the employer. Use it only on request; submitted applications cannot be cancelled.

Instructions

Cancel applications that are queued to be sent or still being prepared, so they are never submitted. Nothing is sent to the employer. A cancellation cannot be undone with these tools. An application that was already submitted cannot be cancelled or withdrawn, and the answer says so for each one. Pass 1 to 25 application_ids from getmattered_get_applications. Cancel only when the user asks. Do not use it for an application waiting for the user's review; use getmattered_reject_applications. Next: getmattered_get_applications to see the new status.

Input Schema

Name	Required	Description	Default
`application_ids`	Yes	Application ids to act on, 1 to 25 (e.g. [1550, 1551]), from getmattered_get_applications

Output Schema

Name	Required	Description
`results`	Yes
`decision`	Yes	The operation that ran: approve, reject, cancel, refine, re_prepare or set_stage.
`attempted`	Yes
`succeeded`	Yes
`notConfirmed`	Yes	True when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.10.2Oct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the consequences an agent actually needs: nothing is sent to the employer, cancellation cannot be undone with these tools, and already-submitted applications are refused with a per-item explanation rather than failing the whole batch. That last detail materially changes how an agent should interpret results.

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?

Front-loaded with the outcome, then constraints, then the sibling routing, then the next step. Six short sentences, each carrying distinct information; no filler or restatement of the tool name.

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?

Covers the destructive, irreversible nature of the call, batch bounds, the partial-failure behavior, the sibling to use instead, and the natural follow-up. An output schema exists so return-shape explanation is correctly omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already states the 1-to-25 limit and id derivation, so the description largely restates it. It does add value by tying the ids back to the workflow ('from getmattered_get_applications'), but adds no new format or ordering semantics beyond the schema.

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 ('Cancel applications') plus the exact scope: applications queued to be sent or still being prepared. It also explicitly separates this from withdrawal of submitted applications, so the boundary of the operation is unambiguous from the first sentence.

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?

Gives explicit when-to-use ('Cancel only when the user asks'), when-not-to-use ('Do not use it for an application waiting for the user's review'), and names the correct alternative (getmattered_reject_applications). It also names the prerequisite retrieval tool and the follow-up step.

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

Deploy Server