Skip to main content
Glama

extract_job_apply_profile_from_resume

Read-only

从用户的一份简历中提取网申档案字段的建议值(不传 resumeId 用最近更新的那份),并列出简历里没有、档案也未填的字段。只返回建议、不保存;用户确认后用 update_job_apply_profile 保存。(需要用户授权,范围 job_applications:read)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_job_apply_profile_from_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdNo简历 ID,从 list_resumes 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already mark the tool read-only and non-destructive, but the description adds behavior beyond them: it states that nothing is saved, discloses the required authorization scope job_applications:read, and describes what is returned (suggested values plus a list of fields missing from the resume and the profile). Those additions go beyond the safety hints that structured fields already provide.

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 description is one compact paragraph, and the main purpose is stated first; the parenthetical notes then cover default behavior and authorization. Every clause carries information, but nested parentheses make the sentence slightly dense and harder to scan.

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

Completeness5/5

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

Because the tool is read-only and simple, has one optional parameter, and has no output schema, the description carries appropriate weight. It covers what the tool returns, what it does not do (save changes), the authorization scope, and the default resume selection. An agent has everything needed to call the tool correctly.

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 schema already explains the resumeId parameter and where to obtain it. The description adds useful behavior that the schema does not state: if resumeId is omitted, the tool uses the most recently updated resume. That meaning goes slightly beyond the baseline for a mostly documented parameter.

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 states a specific verb and resource: it extracts suggested values for job-application profile fields from a single resume, and it also lists fields that are missing from both the resume and the profile. The description contrasts this with update_job_apply_profile, which persists the result, so an agent can distinguish the two tools without opening either schema.

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

Usage Guidelines5/5

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

The description gives explicit when/how guidance: call this tool to get suggestions, and call update_job_apply_profile only after the user confirms to save. It also states that the result does not persist, which is a clear boundary between this tool and the sibling tool that writes changes. It also tells the agent what to do when no resumeId is supplied: use the most recently updated resume.

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