GetMattered

Reject Applications

getmattered_reject_applications

DestructiveIdempotent

Skips applications waiting for review that the user said no to. Nothing is sent. Preparation stays charged.

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_reject_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

A3.5/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real information beyond them: 'Nothing is sent' rules out an outbound notification to the employer, and 'Preparation stays charged' warns that the generated preparation credit is consumed and not refunded. That cost/irreversibility disclosure is exactly the kind of context annotations cannot express. It stops short of stating the resulting application state or what happens to already-reviewed ids.

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 terse sentences, front-loaded with the action and immediately followed by the two side-effect facts an agent most needs. No filler, no restatement of the name.

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?

With only one required parameter, full schema coverage, rich annotations, and an output schema that covers return values, the description supplies what's missing: precondition state and side effects. What is still absent is the post-call application stage and behavior for non-pending ids, but these are minor for a single-parameter bulk mutation.

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%: the array is documented as ids 1 to 25 sourced from getmattered_get_applications, including an example. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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

Purpose3/5

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

The description says it 'skips applications waiting for review' that the user declined, which conveys the resource and the conditional state. However, the verb 'skips' diverges from the tool's own name/title ('Reject') and echoes a sibling, getmattered_skip_matches, so an agent cannot cleanly tell this apart from skipping matches or from getmattered_cancel_applications. The scope is clearer than the action semantics.

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

Usage Guidelines3/5

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

Implicit usage is present: act only on applications 'waiting for review that the user said no to,' which tells the agent the precondition. There is no explicit guidance on when to prefer this over cancel_applications, approve_applications, or repreparation, and no statement about what happens to ids that are not in a pending-review state.

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.