Skip to main content
Glama
jobhunt

jobhunt

by athulanish

check_cv_health

Checks a CV file for common ATS parsing problems—scanned PDFs, tables, missing standard headings or contact details—and counts lines containing numbers.

Instructions

Check a CV file for problems that commonly break ATS parsing: scanned PDFs, tables, missing standard headings, missing contact details, and how many lines contain numbers.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does convey that this is an inspection of a file's structure rather than a mutation, and hints that results include counts ('how many lines contain numbers'). It omits whether the file is read-only, what happens on unreadable/unsupported files, and the shape of the report.

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 front-loaded sentence with the purpose first and the enumerated checks after; no filler. The trailing 'how many lines contain numbers' is the only phrasing that reads slightly awkwardly, but it still carries concrete meaning.

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 simple one-parameter, read-style tool with no output schema or annotations, the description gives a solid account of what is inspected. It leaves gaps on path semantics and on what the caller receives back, which matters because there is no output schema to fall back on.

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

Parameters2/5

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

The single parameter 'path' has 0% schema description coverage, so the description is the only source of meaning. 'CV file' implies the path targets a CV document, but nothing is said about absolute vs relative paths, allowed extensions, or remote vs local access.

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 and resource ('Check a CV file') plus the motivation ('problems that commonly break ATS parsing') and enumerates the exact checks: scanned PDFs, tables, missing headings, missing contact details, numeric line counts. That enumeration effectively separates it from read_cv and compare_cv_to_job, though no sibling is named.

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 by the phrase 'problems that commonly break ATS parsing' — an agent can infer this is a pre-submission diagnostic. There is no explicit statement of when to prefer it over read_cv, nor any prerequisite such as the file needing to be a PDF/DOCX or locally accessible.

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