Skip to main content
Glama

面灵AI 面试助手

abandon_job_application

「不再投递」:把一条投递移出待办,记录保留(已投递的同时移出追踪)。可用 restore_job_application 恢复。回包为读回的状态。(需要用户授权,范围 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
applicationIdYes投递记录 ID,从 list_job_applications 或加入清单的工具回包取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses that the record survives the operation, that already-submitted entries are additionally removed from tracking, that the action is reversible via restore_job_application, and that it requires user authorization with the job_applications:write scope. Those are exactly the traits an agent needs before mutating state.

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?

One short block: the action and its effect lead, the reversibility and authorization notes follow in parentheticals. Every clause (retention, tracking removal, restore path, response shape, auth scope) carries distinct information with no padding.

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?

For a one-parameter mutation with no output schema, the definition covers side effects, reversibility, permission requirements, and the general shape of the response ("回包为读回的状态"). The return-value statement is somewhat terse, which is the only 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 the single applicationId parameter is already documented in the schema, including where to obtain it from list_job_applications. 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.

Purpose4/5

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

The description uses a specific verb and resource ("把一条投递移出待办" – move an application out of the to-do list) and adds a qualifying detail that the record is retained, which distinguishes it from a hard delete like remove_job_application. It never explicitly contrasts itself with remove_job_application by name, so differentiation is implied rather than spelled out.

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?

The 「不再投递」 framing plus the note that submitted applications are also dropped from tracking gives a clear context for when to invoke it, and it names restore_job_application as the undo path. It stops short of stating when to prefer it over remove_job_application or the failure/submission markers.

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