GetMattered

Score Resume

getmattered_score_resume

Scores a resume for ATS compatibility against a job description or for general readiness, returning section scores, matched and missing keywords, and rewrite suggestions.

Instructions

Score a resume for ATS compatibility. Returns an overall score, section scores, the keywords the resume matches and the ones it is missing, and specific rewrite suggestions. Pass job_description to score against a posting, or omit it for a general ATS readiness score. It does not change the user's resume or settings. Requires a connected GetMattered account and uses the user's credits. Do not use it to rewrite the resume; use getmattered_optimize_resume. Next: getmattered_optimize_resume rewrites the resume against the same posting. resume_text is optional: the user can paste or attach a resume in the chat, and you pass its text as resume_text. Without it, the tool uses the resume already on the user's account. In ChatGPT the user can attach a resume file; pass it as resume_file.

Input Schema

Name	Required	Description
`resume_file`	No	In ChatGPT the user can attach a resume file; pass it as resume_file. It is downloaded once, right away: PDF, DOCX or plain text, up to 10 MB.
`resume_text`	No	Full text of the resume. The resume the user pasted or attached in this conversation, as plain text. Omit it to use the resume already on the user's GetMattered account.
`job_description`	No	Full text of the job description (optional, omit for a general ATS readiness score)

Output Schema

Name	Required	Description	Default
`suggestions`	Yes
`overallScore`	Yes
`sectionScores`	Yes
`keywordMatches`	Yes
`missingKeywords`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.9.1Oct 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds context beyond the annotations: no mutation of the user's resume or settings, requires a connected GetMattered account, and consumes the user's credits — which usefully explains why readOnlyHint is false for an otherwise non-mutating tool. It does not cover credit cost magnitude, failure modes, or latency, so it falls short of full behavioral disclosure.

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-loaded with purpose and the targeted-vs-general branch before the caveats, which is the right ordering. Slightly redundant: the getmattered_optimize_resume handoff is stated twice ("Do not use it to rewrite... use getmattered_optimize_resume" then "Next: getmattered_optimize_resume rewrites...").

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?

An output schema covers the return shape, annotations cover the safety profile, and all three parameters are fully described in the schema. The description fills the remaining agent-relevant gaps: auth/credit requirements, the no-side-effects guarantee, and the sibling routing.

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 description coverage is 100%, so baseline is 3. The description clarifies the conversational origin of resume_text (pasted/attached in chat) and that omitting it falls back to the account resume, but it restates schema content and never states precedence when both resume_text and resume_file are supplied.

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 ("Score a resume for ATS compatibility") plus the exact output contents (overall score, section scores, matched/missing keywords, rewrite suggestions). It explicitly distinguishes itself from getmattered_optimize_resume, so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-branch (pass job_description to score against a posting vs. omit for general ATS readiness), a when-not ("Do not use it to rewrite the resume"), and names the correct alternative and logical next step (getmattered_optimize_resume). Nothing is left to inference.

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

Deploy Server