Skip to main content
Glama

AceRound AI Interview Copilot

abandon_job_application

Skip an application: removes it from the to-do list but keeps the record (submitted ones also leave tracking). Undo with restore_job_application. Replies with the status as read back. (Requires the user's sign-in with scope job_applications:write.)

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": {
      "applicationId": "<applicationId>"
    },
    "name": "abandon_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYesApplication id, from list_job_applications or the reply of an add-to-list tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description stays consistent by framing this as a non-destructive skip that preserves the record. It adds real value beyond the annotations: the submitted-application tracking side effect, the undo path, the required sign-in scope job_applications:write, and what the reply contains.

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?

The sentence is front-loaded with the effect and the exception, then the undo route, then the reply, then the auth requirement in parentheses. Every clause carries distinct information with no filler.

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 no output schema, the description usefully states the reply is the status read back, and it covers auth and side effects. Slightly more detail on what statuses can come back or whether a skipped application can be re-added elsewhere would close the remaining gap.

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 applicationId already documents its source (list_job_applications or an add-to-list reply). The description adds no further meaning about the identifier, so the baseline of 3 applies.

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?

The description gives a specific verb (skip/abandon), the resource (a job application), and the exact effect: it leaves the to-do list but the record survives, with submitted applications also leaving tracking. That distinguishes it from a hard-delete sibling such as remove_job_application without needing the other 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?

It establishes the use case (skip rather than delete) and names the corrective action, restore_job_application, for undoing it. It stops short of explicitly contrasting with remove_job_application for permanent deletion, so the agent must infer from the 'keeps the record' clause.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources