Skip to main content
Glama
Sign In

GetMattered

by com.getmattered
OverviewDiscussionsAdmin

Score Resume

getmattered_score_resume

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. resume_text is optional and takes the text of a resume the user pasted or attached in the chat. Without it, the tool uses the resume already on the user's account. In ChatGPT, resume_file takes a resume file the user attached.

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. Changed2 schema fields changed
    • changedInput schema / properties / resume_file / description
      Previous value: -"A resume file the user attached in ChatGPT, as the file itself rather than retyped text. Other clients use resume_text or resume_url. GetMattered reads it once: 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."
    • changedOutput schema / properties / setupStep / description
      Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."
  2. Changed3 schema fields changed
    • 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: -"Only for a resume file the user attached in ChatGPT: pass the attached file here, not retyped text. In any other client pass resume_text or resume_url. 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 rather than retyped text. Other clients use resume_text or resume_url. 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."
  3. Changed1 schema field changed
    • 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: +"Only for a resume file the user attached in ChatGPT: pass the attached file here, not retyped text. In any other client pass resume_text or resume_url. It is downloaded once, right away: PDF, DOCX or plain text, up to 10 MB."
  4. Changed1 schema field changed
    • addedOutput schema / properties / setupStep
      Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false yet destructiveHint=false, and the description explains the tension by noting it 'Changes nothing on the account' while 'Uses AI credits'. It also previews output ('scores, keywords and suggestions') and notes the file is read once, which 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short declarative sentences, front-loaded with the action, effect, and cost before the parameter guidance. No filler or hedging, and each sentence carries a distinct fact.

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?

An output schema exists so return values need not be detailed, and the description still summarizes them. For a three-optional-parameter, cost-bearing AI tool the definition covers safety, cost, and input selection adequately, with only sibling routing left implicit.

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%, so the baseline is 3; the description adds real meaning by explaining the fallback chain (resume_text → account resume → resume_file in ChatGPT) that the field descriptions only partially imply. The file-size and format limits are left to the schema.

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') and scopes it ('for one posting or in general'), which lets an agent separate it from a general job-analysis or rewriting tool. It stops short of naming the nearest siblings such as optimize_resume, so differentiation rests on the verb alone.

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 clear guidance on the three input modes (pasted text, account resume fallback, ChatGPT file) but offers no explicit when-to-use versus alternatives like optimize_resume or analyze_job_description. Usage is implied by the scoring purpose rather than stated against siblings.

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

All GetMattered toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources