Skip to main content
Glama

面灵AI 面试助手

update_job_application_progress

标注一条已投递记录的求职进展。取值:NO_RESPONSE 没回音 / SCREENING_PASSED 简历通过(已读、初筛通过)/ WRITTEN_TEST 笔试 / INTERVIEW 面试邀约或面试中 / OFFER 录用 / REJECTED 未通过。(需要用户授权,范围 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>",
      "progress": "<progress>"
    },
    "name": "update_job_application_progress"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds genuinely new information beyond that: the operation requires user authorization and the job_applications:write scope. It still does not say whether the previous progress value is overwritten or whether transitions are validated, which matters for a state-mutating tool.

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 first sentence states the action, then the enum glossary follows in a compact single-line format, then the auth requirement in parentheses. It is dense but every element carries information; the enum list is long but necessary and could not easily be shortened without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with annotations and no output schema, the core facts (what changes, the allowed values, and the auth scope) are covered. It omits transition or overwrite semantics and says nothing about the response, leaving the agent unsure how to handle out-of-order or repeated updates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage, the description has to fill a real gap, and it does: it gives each of the six progress enum values a concrete operational meaning (for example, SCREENING_PASSED = resume read and passed initial screening), which the bare enum in the schema cannot convey. The applicationId parameter is already documented in the schema, and the description correctly does not repeat it.

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 names a specific verb (标注/update progress) and a specific resource (an already-submitted application record), so the agent knows exactly what changes. It does not, however, distinguish itself from siblings that also change application state, such as mark_job_application_failed or abandon_job_application, whose territory overlaps with the REJECTED value.

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?

Usage is only implied: you call it to record progress on an already-submitted application. There is no explicit statement of when to prefer it over mark_job_application_failed, abandon_job_application, or mark_job_application_submitted, and the description gives no prerequisites or exclusions beyond the auth scope note.

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