Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

match_job

Analyze your resume's fit with a job description and receive targeted improvement suggestions to increase your chances of getting hired.

Instructions

Analyze how well a resume matches a job description and get improvement suggestions

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

Input Schema

NameRequiredDescriptionDefault
resume_idYesResume ID to match
job_descriptionYesFull job description text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it 'analyzes' and 'gets suggestions', but does not clarify if it is read-only, requires authentication, or has side effects. Given siblings that mutate data, this omission is significant.

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 a single sentence that efficiently communicates the action and output. No extraneous information. Front-loaded and to the point.

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 simple schema (2 parameters, no nested objects) and no output schema, the description adequately covers the tool's purpose. However, it lacks details about the format or structure of the improvement suggestions, which would be helpful for an agent.

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?

Both parameters have descriptions in the input schema (100% coverage). The tool description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 tool's purpose: analyzing resume-job match and providing improvement suggestions. It distinguishes from siblings like get_match_score (which likely only returns a score) and optimize_resume_for_job (which modifies the resume).

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?

The description implies usage (when you need match analysis and suggestions), but does not explicitly state when to use this tool over alternatives like get_match_score or optimize_resume_for_job. No exclusions or context provided.

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