Skip to main content
Glama

Score Resume

getmattered_score_resume

Scores a resume against ATS requirements for a specific job posting or general readiness, then returns keyword gaps and suggestions.

Instructions

Scores a resume against applicant tracking systems (ATS), for one posting or in general. Returns scores, keywords and suggestions. Changes nothing on the account. Uses AI credits.

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

Input Schema

NameRequiredDescriptionDefault
resume_fileNoA resume file the user attached in ChatGPT, as the file itself. GetMattered reads it once: PDF, DOCX or plain text, up to 10 MB.
resume_textNoFull text of the resume. The resume the user pasted or attached in this conversation, as plain text. Left out, the resume already on the user's GetMattered account is used.
job_descriptionNoFull text of the job description (optional; without it, the score is a general ATS readiness score)

Output Schema

NameRequiredDescriptionDefault
setupStepNoPresent while account setup is open: the first setup step.
suggestionsYes
overallScoreYes
sectionScoresYes
keywordMatchesYes
missingKeywordsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.13.2
    • changedInput schema / properties / job_description / description
      Previous value: -"Full text of the job description (optional, omit for a general ATS readiness score)"New value: +"Full text of the job description (optional; without it, the score is a general ATS readiness score)"
    • changedInput schema / properties / resume_file / description
      Previous value: -"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."New value: +"A resume file the user attached in ChatGPT, as the file itself. GetMattered reads it once: PDF, DOCX or plain text, up to 10 MB."
    • changedInput schema / properties / resume_text / description
      Previous value: -"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."New value: +"Full text of the resume. The resume the user pasted or attached in this conversation, as plain text. Left out, the resume already on the user's GetMattered account is used."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Addedv1.9.1

TDQS

A3.7/5.0
Behavior4/5

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

Adds two facts the annotations cannot express: the call has no account side effects ('Changes nothing on the account') and it consumes AI credits, which is the real cost signal an agent needs before calling non-idempotent operations. A small tension exists with readOnlyHint=false, but 'changes nothing' plausibly refers to no destructive state change (consistent with destructiveHint=false) rather than a full read-only guarantee.

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?

Three tight sentences: purpose first, then mode, then the two cost/safety facts. 'Returns scores, keywords and suggestions' is largely redundant given an output schema exists, but the rest earns its space.

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 annotations covering the safety profile, a full schema and an output schema, the definition only needs to add cost, side effects and mode selection — and it does all three. The remaining gap is citing a sibling for the adjacent 'improve my resume' intent, which the definition leaves to inference.

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%, including the nested file object's read-once/10 MB constraints and the fallback to the account resume, so the schema already carries the parameter meaning. The description adds the one-argument-per-mode framing but no format or precedence detail beyond the schema, making 3 the correct baseline.

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 ('Scores a resume against applicant tracking systems') plus the output shape ('scores, keywords and suggestions'), which is much more informative than the bare name. It does not explicitly distinguish itself from adjacent siblings like getmattered_optimize_resume or getmattered_analyze_job_description, so an agent must infer the split between scoring and optimizing.

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?

Gives two usable modes ('for one posting or in general') and clarifies the selector for each via the optional job_description, which is genuine usage context. It never states when to pick this over getmattered_optimize_resume, nor any prerequisite such as needing a resume present on the account when both resume inputs are omitted.

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