Skip to main content
Glama

match_jobs_to_resume

Read-onlyIdempotent

Rank public job listings against a saved resume by matching skills with TF-IDF and cosine similarity, optionally using LLM reasoning, then filter by keyword, location, and minimum score.

Instructions

Rank public jobs against a saved resume using TF-IDF and cosine skill similarity with optional LLM reasoning.

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": {
      "id": "<id>"
    },
    "name": "match_jobs_to_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInternal integer ID of saved resume in local database
kwNoOptional job title or keyword query to filter live jobs
locNoOptional location filter (e.g. 'Chennai, India', 'Remote')
limitNoMaximum number of ranked matching jobs to return
min_scoreNoMinimum match score threshold (0-100, default 60)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.8
    • addedInput schema / properties / id / description
      Added value: +"Internal integer ID of saved resume in local database"
    • addedInput schema / properties / kw / description
      Added value: +"Optional job title or keyword query to filter live jobs"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of ranked matching jobs to return"
    • addedInput schema / properties / loc / description
      Added value: +"Optional location filter (e.g. 'Chennai, India', 'Remote')"
    • addedInput schema / properties / min_score / description
      Added value: +"Minimum match score threshold (0-100, default 60)"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the safety profile is handled. The description adds genuine algorithm-level context (TF-IDF/cosine similarity and 'optional LLM reasoning'), which is useful. However, 'optional LLM reasoning' is never explained - no parameter toggles it, no cost/latency implication is noted - and nothing is said about how live job retrieval limits result determinism.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the core action front-loaded and no filler. It is perhaps too terse given the gaps, but nothing is wasted.

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?

With an output schema present, return values needn't be described, and annotations cover the mutation profile. Still, the description leaves unexplained how 'optional LLM reasoning' is activated (no corresponding parameter exists) and how this differs from smart_match_jobs, which is a meaningful omission for a 5-parameter matching tool.

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 all five parameters (id, kw, loc, limit, min_score) are already documented in the schema, and the description adds no further parameter meaning such as scoring scale details or keyword syntax. The baseline of 3 applies when the schema carries parameter semantics.

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 resources: rank public jobs against a saved resume, and even names the technique (TF-IDF + cosine skill similarity, optional LLM reasoning). This tells an agent exactly what the tool produces. It falls short of 5 because it never distinguishes itself from close siblings like smart_match_jobs or search_jobs_advanced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives, despite a crowded sibling set containing at least one obvious overlap (smart_match_jobs). The phrase 'public jobs against a saved resume' only implicitly hints at the use case; an agent must infer the boundaries itself.

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