Skip to main content
Glama

面灵AI 面试助手

upload_resume

上传一份简历文件(PDF / JPG / PNG / WEBP),服务端读出文字后存为用户的新简历,面试与网申可直接选用。文件内容以 base64 传入。返回新简历 ID,可用 get_resume 回读文字。(需要用户授权,范围 resumes: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": {
      "fileName": "<fileName>",
      "fileBase64": "<fileBase64>"
    },
    "name": "upload_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo简历标题;不传取文件名
fileNameYes文件名,如「张三-后端.pdf」
fileBase64Yes文件内容,以 base64 传入

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the required authorization scope resumes:write, that server-side text extraction occurs, and that a new resume ID is returned. It does not say whether an existing resume is replaced, nor any file-size or page limits, which are the remaining behavioral unknowns for an upload mutation.

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?

Front-loaded with the verb, resource and formats, followed by effect, encoding, return value and auth scope in a compact sequence with no filler. The trailing parenthetical for the auth scope is slightly tacked-on but still useful information.

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 3-parameter upload mutation with no output schema, the description covers what happens server-side, what is returned (new resume ID), how to read the text back, and the auth requirement. Only edge-case behavior (replacement semantics, size limits, failure modes) is missing.

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; the description earns extra credit by adding the accepted file formats (PDF/JPG/PNG/WEBP) and confirming base64 encoding, which the schema does not state. It does not mention the title defaulting behavior, but that is already documented in the schema.

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?

States a specific verb and resource (upload a resume file), the accepted formats (PDF/JPG/PNG/WEBP), and the downstream effect (server extracts text and stores it as the user's new resume, selectable for interviews and job applications). It is clearly distinguishable from get_resume (read-back) and from the sibling text-based creation path.

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?

Gives clear context for use: file content is supplied as base64, and the resulting resume can be直接 selected for interviews and job applications; it also routes the agent to get_resume for reading the extracted text. It does not explicitly contrast with the text-input alternative create_resume_from_text, so the when-not guidance is only implicit.

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