Skip to main content
Glama

Nectar Jobs

Match jobs to a CV

recommend_jobs
Read-onlyIdempotent

Rank jobs by how well they match a résumé or free-text description of what the candidate wants. Returns the best-matching jobs first.

``country`` (ISO-2, e.g. GB) or ``location`` (a city or region) is REQUIRED — ask the seeker
where they can work rather than guessing. Semantic ranking over every country returns the
nearest postings on earth, most of which the person cannot take.

``resume_text``: only about the first 400 words shape the ranking; anything after them is not
read. For a longer CV, send what defines the person's next role first: the role they want,
their headline, their recent roles and their key skills, not the whole document in order.

Ranking is purely semantic; the filters are hard. ``seniority`` (intern, junior, senior,
staff, principal, manager, director) filters to exactly that tag — many postings carry none,
so only pass it when the seeker insists.

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>"
    },
    "name": "recommend_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
remoteNo
countryNo
categoryNo
locationNo
seniorityNo
salary_minNo
resume_textYes
employment_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the 400-word truncation on resume_text, that ranking is purely semantic while filters are hard, that seniority filters to an exact tag and many postings carry none, and that omitting location degrades results badly. These are non-obvious behavioral traits an agent could not infer from schema or annotations.

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?

Front-loads the core purpose in one sentence, then groups the warnings by the fields that carry risk, using backticks to tie prose to parameter names. Every sentence adds a constraint or a failure mode; nothing is padding.

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?

With an output schema present, return values need no explanation, and the description covers the highest-risk inputs and the ranking semantics thoroughly. The remaining gap is the unannotated constraint parameters, notably salary_min's unit/currency and what limit does, which an agent would have to guess.

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 0%, so the description must carry parameter meaning, and it does well for resume_text, country, location and seniority. However, five of nine parameters — limit, remote, category, salary_min, employment_type — receive no explanation at all, leaving the salary_min unit/currency and the limit behavior undocumented.

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 resource: "Rank jobs by how well they match a résumé or free-text description," and adds that results come back best-first. The semantic-ranking-versus-hard-filters line further sharpens what the tool actually does. It does not name a sibling (e.g. search_jobs or find_similar_jobs) to delimit itself, so it falls just short of 5.

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?

Gives explicit operational guidance: country or location is REQUIRED and the agent should ask the seeker rather than guess, with the rationale (global semantic ranking returns unworkable postings). It also says to pass seniority only when the seeker insists. There is no tool-level routing guidance versus keyword search siblings, so it is clear context without full alternative coverage.

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