GetMattered

Cancel Applications

getmattered_cancel_applications

DestructiveIdempotent

Stops applications that are queued, being prepared or waiting for review, so they are never submitted. Any preparation already done stays charged. A submitted application cannot be cancelled.

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": {
      "application_ids": "<application_ids>"
    },
    "name": "getmattered_cancel_applications"
  }
}

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, one of approve, reject, cancel, refine, re_prepare or set_stage.
`attempted`	Yes
`setupStep`	No	Present while account setup is open: the first setup step.
`succeeded`	Yes
`notConfirmed`	Yes	True when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

changedOutput schema / properties / decision / description

Previous value: -"The operation that ran: approve, reject, cancel, refine, re_prepare or set_stage."New value: +"The operation that ran, one of approve, reject, cancel, refine, re_prepare or set_stage."

changedOutput schema / properties / results / items / properties / status / description

Previous value: -"Our own record after the action. Never proof the employer received it."New value: +"Our own record after the action, which is not proof the employer received it."

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed2 schema fields changedNov 8, 2026

removedOutput schema / properties / confirmToken

Removed value: -{
-  "description": "Approve of one email application only: nothing was sent yet. Show the user the exact email, then pass this as confirm_token with the same application id once they say yes. Works once, for 10 minutes, and only while the email is unchanged.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "decision",
-  "results",
-  "succeeded",
-  "attempted",
-  "notConfirmed",
-  "confirmToken"
-]New value: +[
+  "decision",
+  "results",
+  "succeeded",
+  "attempted",
+  "notConfirmed"
+]

Changed2 schema fields changedNov 8, 2026

addedOutput schema / properties / confirmToken

Added value: +{
+  "description": "Approve of one email application only: nothing was sent yet. Show the user the exact email, then pass this as confirm_token with the same application id once they say yes. Works once, for 10 minutes, and only while the email is unchanged.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "decision",
-  "results",
-  "succeeded",
-  "attempted",
-  "notConfirmed"
-]New value: +[
+  "decision",
+  "results",
+  "succeeded",
+  "attempted",
+  "notConfirmed",
+  "confirmToken"
+]

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare destructiveHint and idempotentHint, yet the description still adds non-obvious consequences: preparation work already performed 'stays charged' (a real cost to the caller) and submitted applications are out of scope. That is exactly the behavioral context annotations cannot express.

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?

Three short sentences, ordered from effect to cost to exclusion, with no filler. The eligibility constraint is front-loaded.

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 single-parameter mutation with rich annotations and an output schema, the description covers effect, eligible states, the billing side effect, and the hard precondition. Nothing an agent needs to decide or invoke 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 coverage is 100%, and the schema itself documents the 1–25 id list, the id source tool, and examples. The description adds nothing about the parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('stops applications') plus the exact eligibility states (queued, being prepared, waiting for review). It is clearly distinct from mutation siblings like approve/reject, though it never names the closest alternative (reject_applications) to sharpen the boundary.

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 positive conditions for use (only certain pre-submission states) and an explicit exclusion ('A submitted application cannot be cancelled'). Missing is any routing to alternatives such as rejecting an already-submitted application.

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

All GetMattered 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.