Skip to main content
Glama

Check how an ATS reads a resume

checkResumeForAts
Read-onlyIdempotent

Renders one of the candidate's resumes to PDF (their default resume draft, or a draftId from manageResumeVersions or listTailoredResumes) and reads the text back the way applicant tracking systems do: is the text readable, is their name at the top, do email and phone come through, are the section headings there and in order, are employers in order, do bullets read whole, is it one column. Each check comes with a plain explanation. Nothing is saved. Takes about ten seconds.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "checkResumeForAts"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdNoA resume draft; the default draft when absent.

Output Schema

NameRequiredDescriptionDefault
textYesThe first 4,000 characters of text an ATS extracts from the PDF.
pagesYes
totalYes
checksYes
passedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that nothing is saved, that each check returns a plain explanation, that the call takes about ten seconds, and that inputs and results are privately recorded for usage tracking and support. Latency, persistence, and data-handling context are all things annotations cannot convey.

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?

Front-loads the action and its inputs, then lists the checks compactly and closes with the two constraints an agent cares about (nothing saved, ~10 seconds). The trailing privacy sentence is boilerplate but plausibly compliance-required, so it minimally detracts.

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 single optional-UUID tool with full schema coverage, an output schema, and read-only annotations, this covers everything needed to invoke it correctly: what it does, which input to pass, where that input comes from, what is returned conceptually, cost, and side effects.

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% with the draftId documented as 'the default draft when absent', so the baseline is 3. The description adds value by restating the default behavior and, more importantly, naming the two sibling tools that supply a valid draftId, which the schema does not say.

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 and resource: renders a resume draft to PDF and reads the text back the way an ATS does, then enumerates the concrete checks (name at top, contact details, heading order, employer order, bullets, single column). This is clearly distinguishable from generation tools like generateResumePdf or reviewTailoredResume.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the input source explicitly — the candidate's default resume draft, or a draftId obtained from manageResumeVersions or listTailoredResumes — which tells the agent when this tool is applicable. It stops short of stating when to prefer a sibling such as checkApplicant or reviewTailoredResume, so there is no explicit exclusion guidance.

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