Skip to main content
Glama

面灵AI 面试助手

upload_job_apply_attachment

上传一个网申附件(简历附件、学生证、成绩单、证件照)并存入用户的网申档案对应字段,覆盖原有文件。文件内容以 base64 传入,支持 PDF 与 JPG / PNG / WebP,上限 8MB。回包为读回的档案字段。(需要用户授权,范围 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": {
      "field": "<field>",
      "fileName": "<fileName>",
      "fileBase64": "<fileBase64>"
    },
    "name": "upload_job_apply_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesresumeFile 简历附件 / studentIdFile 学生证 / transcriptFile 成绩单 / photoFile 证件照
fileNameYes文件名,含扩展名
fileBase64Yes文件内容,base64

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?

Beyond the annotations (readOnly=false, destructive=false, openWorld=false) the description discloses the overwrite of an existing file, the base64 transport encoding, supported MIME types, an 8MB cap, the required authorization scope job_applications:write, and what the response contains (the re-read profile field). The overwrite wording sits in mild tension with destructiveHint=false, but because the description actually warns the agent about replacement it informs rather than misleads.

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?

One dense paragraph that front-loads the action and the target field, then constraints, then the response shape. Every clause carries information, though the authorization requirement is buried in a trailing parenthetical where it is easy to miss before assembling the payload.

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?

For a 3-parameter mutation tool with no output schema, the description covers everything an agent needs: what is written where, that prior content is replaced, encoding, accepted formats, size limit, permission scope, and the shape of the return value.

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 already 100%, so the field enum and filename/base64 descriptions are documented structurally. The description still adds constraints the schema does not carry: which file formats are accepted and the 8MB size ceiling that applies to the base64 payload, which is real meaning beyond the schema.

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?

Names a specific verb (upload) plus the resource (a job-application attachment) and states exactly where it lands (the corresponding field of the user's job-application profile) and that it replaces the existing file. The four supported field types (resume, student ID, transcript, ID photo) make the operation concrete, though it never says how it differs from nearby tools such as upload_resume or extract_job_apply_profile_from_resume.

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 is implied rather than stated: the agent can infer this is the path for attaching resume/ID/transcript/photo files to a profile, and the size and format limits (8MB; PDF, JPG/PNG/WebP) tell it when the call is valid. There is no explicit when-not guidance and no named alternative for plain resume uploads or for parsing a resume into profile fields.

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