Skip to main content
Glama

Check resume

score_resume
Read-onlyIdempotent

Use this when the person asks whether a resume or CV is good, ATS-friendly or ready to send, or asks for its score or what to fix. Takes the attached resume file (file), pasted resume text (sourceText) or a saved resume (resumeId); a job ad is optional. Works signed out. Returns CVEmber's ATS score, 0-100, and the first things to fix. Reads only and saves nothing. Do not use to save or edit a resume.

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

Input Schema

NameRequiredDescriptionDefault
fileNoThe resume file the person attached (PDF, Word, text or a photo), passed as is.
contentNoA pasted resume (contact, summary, experience, education, skills), when there is no resumeId.
keywordsNoKeywords from the job ad to check for; read from the ad when omitted.
resumeIdNoA resume id from list_resumes.
sourceTextNoText the person pasted, copied exactly.
jobDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / file
      Added value: +{
      +  "description": "The resume file the person attached (PDF, Word, text or a photo), passed as is.",
      +  "properties": {
      +    "download_url": {
      +      "description": "Download link of the attached file.",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / sourceText
      Added value: +{
      +  "description": "Text the person pasted, copied exactly.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / content
      Added value: +{
      +  "description": "A pasted resume (contact, summary, experience, education, skills), when there is no resumeId.",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "resumeId"
      -]New value: +[]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the bar is lower; the description nonetheless adds real context the annotations cannot convey: 'Works signed out' (no auth needed) and the return payload (0-100 ATS score plus the first things to fix), which matters because there is no output schema. 'Reads only and saves nothing' restates the annotations rather than extending them, keeping it just short of top marks.

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?

Three compact sentences, front-loaded with the trigger and then the inputs, output and exclusion in descending order of importance. No filler, no repetition of the tool name, and the return-value sentence earns its place given no output schema.

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 read-only scoring tool with no output schema and zero required parameters, the description covers everything an agent needs: when to call it, the three interchangeable input sources, that the job ad is optional, that no auth is required, that nothing is persisted, and what comes back. No material decisions are left to inference.

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?

With 83% schema coverage the baseline is 3, but the description adds the meaningful selection rule across input modes — attached file, pasted sourceText, or saved resumeId — plus that the job ad is optional, which the schema leaves implicit given there are zero required parameters. It omits the `content` and `jobDescription` parameters entirely, so the schema still has to be consulted for those.

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/CV for ATS readiness') and explicitly carves itself out from write-oriented siblings with 'Do not use to save or edit a resume.' The parenthetical list of triggers (good, ATS-friendly, ready to send, score, what to fix) makes it distinguishable from update_resume, tailor_resume and create_resume at a glance.

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?

Trigger conditions are stated concretely ('when the person asks whether a resume or CV is good, ATS-friendly or ready to send') and there is an explicit exclusion for save/edit. What it lacks is naming the alternative to route to when the user wants changes applied rather than diagnosed (e.g., tailor_resume), so the negative case is covered but the positive-elsewhere case is only implied.

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