Skip to main content
Glama

Check a resume against a job post

analyze_resume_job

Use this when the user asks how well their resume matches a specific job post, without rewriting it. Pass the resume text (cvText), the job post text (offerText) and the guestToken. Returns an operationId and a coverage score from 0 to 100 with the requirements demonstrated, partly demonstrated, missing or unclear, each with its job post and resume evidence. The score is neither an ATS guarantee nor a hiring probability. Do not use to tailor the resume or produce a PDF; use create_tailored_resume. Identical retries reuse the operation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guestToken": "<guestToken>",
      "cvText": "<cvText>",
      "offerText": "<offerText>"
    },
    "name": "analyze_resume_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvTextYes
offerTextYes
guestTokenYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-read-only, non-destructive, closed-world), the description discloses the return payload (operationId plus 0-100 coverage score with categorized requirements and evidence), sets expectation limits ('neither an ATS guarantee nor a hiring probability'), and documents idempotency ('identical retries reuse the operation'). It does not mention auth or lifetime expectations for guestToken, which is the remaining behavioral gap.

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?

Four tight sentences, front-loaded with the trigger, followed by inputs, then outputs, then exclusions. No filler and no restatement of the title.

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?

The description covers trigger, inputs, return shape, interpretation caveats, retry behavior, and the boundary against the tailoring sibling — more than enough for a three-parameter analytical tool, especially with an output schema carrying return details.

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 description coverage is 0%, so the description must carry the burden; it maps cvText to resume text and offerText to job post text, clarifying content that the bare property names only imply. However guestToken is passed as 'the guestToken' with no indication of where it comes from (a sibling create_guest_context exists) or its lifetime, leaving one of three required params under-explained.

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 ('how well their resume matches a specific job post') plus the key constraint 'without rewriting it'. It explicitly distinguishes itself from the sibling create_tailored_resume, so an agent can route between the two 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 trigger ('when the user asks how well their resume matches a specific job post'), an explicit exclusion ('Do not use to tailor the resume or produce a PDF'), and names the correct alternative. When/when-not/alternative are all present.

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