Skip to main content
Glama

offerquest_mcp_ats_keywords

ATS keyword gap report: compares a resume with one job posting and lists must-have and nice-to-have keywords that are missing, plus what is already covered. The resume is processed in memory only and never stored or logged.

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": {
      "resume_text": "<resume_text>",
      "job_id_or_description": "<job_id_or_description>"
    },
    "name": "offerquest_mcp_ats_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_textYesPlain-text resume (max 20,000 characters).
job_id_or_descriptionYesEither the 10-character Job ID from fetch_and_format_jobs / rank_jobs results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it usefully discloses that the resume is processed in memory only and never stored or logged — meaningful privacy context an agent cannot get elsewhere. It still omits any statement about rate limits, permissions, or error behavior.

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?

Two tight sentences with the tool's purpose front-loaded and the privacy guarantee tacked on after; every clause earns its place with no filler.

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?

For a two-parameter tool with no output schema, the description does well by enumerating what the report contains (missing and covered keywords) and flagging the in-memory handling. A brief note on output shape or failure modes would close the remaining gap.

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%, so both parameters are already documented in the schema. The description adds only the implicit constraint of a single job posting and does not expand on formats or the Job ID alternative beyond what the schema states, matching the baseline 3.

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?

The description names a specific verb and resource: it compares a resume against one job posting and produces missing must-have/nice-to-have keywords plus coverage. This is functionally distinct from the fetch/rank siblings, though it never names them, so differentiation is left implicit.

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?

Usage is implied by 'compares a resume with one job posting', letting an agent infer the task context. There is no explicit when-to-use guidance, no prerequisites, and no mention of the sibling tools or when to prefer them.

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