Skip to main content
Glama

ResumeVsJob Batch

Check resumes against a job posting

check_resumes

Scores 1–30 resumes against one job posting (ATS keyword match). Returns, per resume: match score 0–100, verdict, missing required and other keywords, missing sections, contact details present, and the top fixes. Results are sorted best first. Each resume uses 1 credit of a license key; without a key only the score is returned (max 3 resumes). Resume text is processed in memory and not stored.

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": {
      "job_posting": "<job_posting>",
      "resumes": "<resumes>"
    },
    "name": "check_resumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumesYesResumes as plain text.
job_postingYesFull text of the job posting (responsibilities + requirements).
license_keyNoGumroad license key of the 30-resume pack. Optional if the connector URL already has ?key=.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the sparse annotations (readOnlyHint=false, openWorldHint=false) by disclosing a credit cost per resume, the degraded no-key mode with a hard 3-resume limit, result ordering (best first), and that resume text is processed in memory and not stored. The credit consumption also explains why readOnlyHint is false, so there is no contradiction with the no-storage claim.

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 dense sentences, front-loaded with the action and result shape before cost and privacy details. Every sentence carries distinct information (what it does, what it returns, what it costs, how data is handled) with no restatement of the name.

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?

There is no output schema, and the description compensates fully by enumerating the returned fields (score 0–100, verdict, missing keywords, missing sections, contact details, top fixes) and their sort order. Combined with the licensing and privacy notes, an agent has everything needed to call it and interpret results.

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 100%, so the schema already documents all three parameters; the description still adds useful semantics, namely the 1–30 resume bound and the per-resume credit accounting. It does not add much about job_posting text requirements beyond what the schema says, so this sits above the baseline but not at the top.

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, resource, and scope: "Scores 1–30 resumes against one job posting (ATS keyword match)." The bounding (1–30 resumes, one posting, ATS keyword matching) makes it immediately distinguishable from the sibling credits_left tool.

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?

Explains the operational condition that governs use: each resume costs 1 credit, and without a license key only scores are returned with a 3-resume cap, so an agent knows what to expect in each mode. It does not explicitly route the agent to credits_left for balance checks or state when not to use this tool, which keeps it short of a 5.

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