Skip to main content
Glama
jobhunt

jobhunt

by athulanish

read_cv

Extract and return the full text from a CV file (PDF, DOCX, TXT, or MD) so you can analyze, compare, or check it for ATS issues.

Instructions

Read a CV file (PDF, DOCX, TXT or MD) from the user's computer and return its full text.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It helpfully discloses accepted formats and that the full text is returned, but says nothing about failure modes (missing/unreadable file, unsupported format), size or page limits, or whether extraction is lossy for scanned PDFs.

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?

A single well-formed sentence with no filler; the verb and resource are front-loaded and format support follows. Slightly more structure (e.g., a note on return/error behavior) would cost nothing but is absent.

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 one-parameter read tool with an output schema that already defines the return shape, the description covers what is being read, from where, and in which formats. Only edge-case behavior around unreadable paths is missing, which is a modest gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'path' parameter is undocumented in the schema, so the description must compensate. It adds only that the path points at a file on the user's computer, leaving absolute vs. relative paths, extensions, and quoting conventions unaddressed.

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 (Read) and resource (a CV file), names the supported formats (PDF, DOCX, TXT, MD), identifies the source location (the user's computer), and states what is returned (its full text). This clearly separates it from siblings like check_cv_health or compare_cv_to_job, which analyze rather than extract.

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 tool for pulling raw CV text before analysis. It never states when to prefer this over check_cv_health or compare_cv_to_job, nor any prerequisites such as the file needing to already exist locally.

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