Skip to main content
Glama

analyze_resume

Read-onlyIdempotent

Parse resume PDF, DOCX, TXT, or MD files locally into structured skills, experience, and contact details without external API calls.

Instructions

Parse resume PDF/DOCX/text locally into structured skills, experience, and contact info without external calls.

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": "analyze_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute local file path to resume file (.pdf, .docx, .txt, or .md)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / path / description
      Added value: +"Absolute local file path to resume file (.pdf, .docx, .txt, or .md)"
  2. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real value by saying parsing happens locally with no external calls, which matters for resume privacy, but it says nothing about failure modes (unsupported format, bad path, size limits). Note a mild tension with openWorldHint=true, since local file-only parsing is arguably not open-world.

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?

A single front-loaded sentence that carries the verb, formats, output fields, and the local-execution guarantee with no filler. Every clause earns its place.

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 one documented parameter, full annotations, and an output schema covering return values, the description supplies what an agent needs to select and call it. Only error/edge-case behavior is unaddressed, which is a minor gap for a parser.

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?

Only one parameter and the schema documents it fully at 100% coverage, including accepted extensions (.pdf, .docx, .txt, .md) and the absolute-path requirement, so the baseline is 3. The description slightly reinforces the accepted formats (PDF/DOCX/text) but adds nothing beyond the schema, keeping this near baseline rather than high.

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?

States a specific verb (parse) and resource (resume) plus what the output contains: structured skills, experience, and contact info. This distinguishes it from insight/matching siblings like get_resume_insights and tailor_resume, though it never names an alternative explicitly.

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 only implied: the agent can infer this is the low-level entry point that turns a resume file into structured data before calling analysis tools. There is no statement of when to prefer it over get_resume_insights or match_jobs_to_resume, and no prerequisites or exclusions.

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