Skip to main content
Glama

import_resume

Copies an authorized resume file from an absolute path into a separate library without altering the source; supports PDF, DOCX, TXT, and MD.

Instructions

用户授权读取的简历绝对路径。复制原文件到独立资料库,不修改源文件。支持 PDF/DOCX/TXT/MD。

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": {
      "path": "<path>"
    },
    "name": "import_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and destructiveHint=false, and the description adds meaningful context on top: the operation copies rather than moves, and the source file is explicitly not modified. It also lists supported formats (PDF/DOCX/TXT/MD), which is behavior an agent cannot obtain from the annotations or the bare schema. It stops short of describing what happens on duplicate imports or where the library lives.

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?

Three compact sentences with no filler, covering the parameter, the copy semantics, and supported formats. The only structural weakness is that the verb of the tool is not in the leading position, so the most important information is not strictly front-loaded.

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 single-parameter tool with no output schema and light annotations, the description covers format support and the non-destructive copy behavior, which is the core of what an agent needs. It leaves open the return value (no identifier or path is described) and duplicate-handling behavior, which matter for a tool that creates a stored copy.

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 description coverage is 0% for the single path parameter, so the description carries the burden and does so reasonably: it specifies that the value must be an absolute path and that the user must have authorized reading that file. It does not give an example path or state what happens if the path is invalid or the format is unsupported.

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 states a concrete action and resource: copy the original resume file into an independent library and leave the source file untouched, which distinguishes it from a resume-editing or version-saving sibling. The opening sentence, however, describes the parameter (an absolute path the user authorized) rather than the tool's action, so the purpose arrives second and is slightly less front-loaded.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as propose_resume_changes or save_resume_version, so an agent must infer from the verb alone that this is the entry point for bringing an existing file into the workspace. The authorization note implies a prerequisite, but the conditions that select this tool over its siblings are never stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.