Skip to main content
Glama

Approve Applications

getmattered_approve_applications
Destructive

Approves and submits selected waiting job applications to employers under your name, using one application credit per submission. This action is irreversible.

Instructions

Submits waiting applications to their employers under the user's name. Spends one application each. It cannot be undone.

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_approve_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idsYesApplication ids to act on, 1 to 25 (e.g. [1550, 1551]), from getmattered_get_applications

Output Schema

NameRequiredDescriptionDefault
resultsYes
decisionYesThe operation that ran, one of approve, reject, cancel, refine, re_prepare or set_stage.
attemptedYes
setupStepNoPresent while account setup is open: the first setup step.
succeededYes
notConfirmedYesTrue when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.13.2
    • 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."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Addedv1.10.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the bar is lower, yet the description adds two genuinely non-obvious facts: each approval consumes one application credit and submissions go out under the user's own name. 'It cannot be undone' partly restates destructiveHint, which keeps this from a 5.

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?

Three short sentences, front-loaded with the action and its consequence. The final sentence is somewhat redundant with the destructive annotation, but it is short enough to justify the emphasis.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description fills the remaining gap that matters most — the credit cost per approval and the attributed identity — leaving nothing an agent needs before calling it.

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% and the single parameter already documents the 1–25 array bounds and its source tool (getmattered_get_applications). The description adds nothing about the ids, 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?

The description gives a concrete verb+resource pair: it submits *waiting* applications to *employers* under the user's name. The 'waiting applications' qualifier distinguishes it from sibling getmattered_apply (new applications), but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus the obviously adjacent siblings (reject_applications, cancel_applications, reprepare_applications, set_application_stage). The 'waiting applications' wording implies a precondition, but prerequisites and exclusions are left entirely to inference.

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