Skip to main content
Glama
jobhunt

jobhunt

by athulanish

compare_cv_to_job

Compare a CV with a pasted job description to identify which top job terms appear in the CV and which are missing.

Instructions

Compare a CV with a pasted job description. Returns which of the job's top terms appear in the CV and which do not. Crude overlap, so judge each missing term before using it.

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": {
      "cv_path": "<cv_path>",
      "job_description": "<job_description>"
    },
    "name": "compare_cv_to_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
cv_pathYes
job_descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does add real value by naming the output shape (terms present vs. absent) and warning that the overlap is crude. It omits operational behavior an agent needs, such as whether cv_path is read from disk, accepted file formats, what happens on a bad path, and any size limits.

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?

Three short sentences, front-loaded with the action and return value, followed by the caveat. Nothing is padded or redundant, and every sentence adds information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small two-parameter tool with no output schema and no annotations, the description covers purpose and output shape adequately. It falls short on the file-input semantics of cv_path and on failure behavior, which matter because there is no structured field supplying them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 supply parameter meaning. 'Pasted job description' helpfully signals that job_description is inline text rather than a path, but cv_path gets no explanation at all — no format, relative-vs-absolute path, or file type guidance.

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?

States a specific verb and both resources ('Compare a CV with a pasted job description') and even declares what it returns ('which of the job's top terms appear in the CV and which do not'). That is well beyond a restatement of the name, though it never positions itself against siblings like check_cv_health or check_job_risk.

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 trailing sentence gives interpretation guidance ('Crude overlap, so judge each missing term before using it'), which is genuine usage advice. However, it never says when to reach for this versus the sibling CV/job tools, so the when-to-use decision is only implied by the purpose statement.

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