Skip to main content
Glama

面灵AI 面试助手

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": "restore_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationIdYes投递记录 ID,从 list_job_applications 或加入清单的工具回包取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description adds genuinely useful facts: user authorization is required with scope job_applications:write, the response is the read-back status, and the call will not resubmit. Those additions are worthwhile, but the description does not say what happens if the record is not in the abandoned state, nor what errors to expect.

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?

The definition is a compact, front-loaded statement: the target state comes first, then the two branches, then the return information and the authorization note. It contains almost no filler, although the parenthetical authorization note is dense.

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 non-destructive mutation, this definition covers the action, the state condition, the branching outcome, the authorization scope, and the response shape. No output schema exists, but the description compensates by saying the response is the read-back status; only failure or edge-case behavior is unstated.

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?

The schema coverage is 100% for the single required applicationId, and the schema itself explains where to get the ID. 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.

Purpose4/5

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

The description uses a specific verb meaning restore and applies it to records in the「不再投递」(no-longer-applying) state, and it spells out two outcomes: records never submitted go back to the apply list, while submitted ones go back to application tracking. This contrasts the tool with the abandon/mark-failed state implicitly, though it never names the sibling that creates that state.

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?

Usage context is clear: apply it to records that have been abandoned, and the description states which resulting bucket each record lands in depending on whether it was submitted. It also clarifies that restoration will not resubmit the application, which prevents a misuse. There is no explicit statement of when not to use it and no tool it names as an alternative.

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