Skip to main content
Glama

面灵AI 面试助手

select_job_application_resume

指定某一条投递使用哪份简历;resumeId 传 null 改回基础简历。回包为读回的简历。(需要用户授权,范围 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>",
      "resumeId": "<resumeId>"
    },
    "name": "select_job_application_resume"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write. The description adds real value beyond them: it discloses the required authorization scope job_applications:write, states that passing null reverts to the base resume, and says the response is the read-back resume object. It does not cover failure modes, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses cover purpose, the null edge case, the return payload, and the auth scope, with the core action front-loaded. Every sentence earns its place and nothing is padded.

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 only two fully documented parameters, no output schema, and explicit annotations, the description supplies what is missing: auth scope, null semantics, and the shape of the response. It would reach 5 if it noted constraints such as whether the resume must belong to the same user/profile.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the null branch of resumeId specifically means 'revert to the base resume' rather than merely 'empty'. It also clarifies the RESUME return value ties to whichever resume was set.

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 precise verb and resource: assign a specific resume to a specific job application. No sibling tool performs this operation, so the intent is unambiguous, but the description never explicitly distinguishes itself from adjacent application-mutation tools such as update_job_application_progress.

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

Usage Guidelines3/5

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

Usage context is implied by the operation (you must already have both an applicationId and a resumeId from prior list calls, which the schema covers). The null case is explained as a revert path, which is useful, but there is no explicit when-to-use guidance, prerequisites, or mention of alternatives such as changing the application's resume via a different tool.

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