Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

analyze_resume_gaps

Compare a resume against a job description to identify missing keywords, skill gaps, and areas for improvement.

Instructions

Analyze resume against a job description to identify missing keywords, skills gaps, and improvement suggestions. More detailed than match_job.

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_id": "<resume_id>",
      "job_description": "<job_description>"
    },
    "name": "analyze_resume_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_idYesResume ID to analyze
job_descriptionYesJob description to compare against

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of disclosure. It mentions the analytical purpose but does not state behavioral traits such as side effects (mutations), permission requirements, rate limits, or whether the tool is read-only.

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?

The description is concise with two sentences. The first sentence delivers the core purpose, and the second provides a comparison to a sibling. No redundant or irrelevant information.

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?

Given the tool has two parameters and no output schema, the description adequately explains the expected outputs (missing keywords, skills gaps, improvement suggestions) and differentiates from a sibling. It is complete enough for an agent to understand the tool's function.

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 coverage is 100% with clear descriptions for both parameters. The tool description adds context by mentioning the job description, but does not provide additional semantic detail beyond what the schema already offers.

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?

The description clearly states the verb ('Analyze'), resource ('resume against a job description'), and specific outputs ('missing keywords, skills gaps, improvement suggestions'). It also distinguishes from sibling 'match_job' by noting it is more detailed.

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?

The description provides explicit context for when to use this tool over 'match_job' by stating it is more detailed. However, it does not offer guidance on when not to use it or comparisons with other siblings like 'optimize_resume_for_job' or 'check_ats_compatibility'.

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

Deploy Server

Other Tools