Skip to main content
Glama

remoty.work Remote Jobs

match_jobs_to_profile

Read-onlyIdempotent

Rank live remote jobs against a job seeker's profile (titles, skills, level, country, minimum pay) and say why each fits and what it also asks for. Build the profile from the person's resume or what they told you; only jobs they can take from their country are ranked.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "match_jobs_to_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillsNoSkills from their resume or what they said, e.g. ["Rust", "PostgreSQL", "Kubernetes"].
titlesNoRoles the person wants or has held, e.g. ["Backend Engineer", "Platform Engineer"].
countryNoWhere the person lives: a country name or ISO code. Without it, only jobs open worldwide are ranked.
seniorityNoOne of: intern, junior, mid, senior, staff, lead, principal, head, director.
min_salary_usdNoLowest yearly pay they would accept, in US dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds context annotations don't carry: it discloses what the result contains ('say why each fits and what it also asks for') and the country-restriction behavior ('only jobs they can take from their country are ranked'), which is meaningful for interpreting results.

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?

Two sentences with no filler; the core action is front-loaded and the second sentence adds operating instructions. Phrasing like 'what it also asks for' is slightly informal, but no sentence is wasted.

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?

There is no output schema, so the description must convey what comes back — and it does, stating that each match includes why it fits and what else it requires. Combined with the country-ranking caveat, an agent has enough to call it correctly; only the volume/format of results is unspecified.

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 every parameter is already documented in detail, making the description's enumeration of titles/skills/level/country/minimum pay largely redundant. It adds only a small gloss by mapping 'level' to the seniority field and framing the profile-construction intent. Baseline 3 applies when the schema carries the semantic load.

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?

The description states a concrete verb and resource — 'Rank live remote jobs against a job seeker's profile' — and enumerates the matching dimensions (titles, skills, level, country, minimum pay). It is clearly a ranking/match tool rather than a plain search, but it never names its siblings (search_remote_jobs, remote_jobs_open_to_country), so the distinction from those is left implicit.

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?

It gives useful operating context ('Build the profile from the person's resume or what they told you') and a scoping rule ('only jobs they can take from their country are ranked'), which tells the agent how to populate inputs. However, it never says when to prefer this over search_remote_jobs or remote_jobs_open_to_country, so the alternative-selection guidance is only implied.

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