Skip to main content
Glama

aitrainer.work AI training jobs

Match AI training jobs to a profile

match_jobs_to_profile
Read-onlyIdempotent

Rank open AI training and AI evaluation roles for one person by their profession, skills, languages, country and minimum hourly pay (USD). Use when the user describes their own background, e.g. "I am a nurse in Canada". Returns up to 10 roles, highest match first, each with the reasons it fits. Nothing about the person is stored.

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": {
      "role": "<role>"
    },
    "name": "match_jobs_to_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesProfession or main background, e.g. "registered nurse", "Python developer", "corporate lawyer".
limitNoMatches to return, default 6.
skillsNoSpecific skills or specialties, e.g. ["cardiology", "ICU"].
countryNoCountry the person lives in (English name). Only roles open to it are returned.
languagesNoLanguages the person speaks fluently, in English, e.g. ["English", "Spanish"].
min_hourly_payNoLowest acceptable hourly pay in USD.

Output Schema

NameRequiredDescriptionDefault
jobsYes
returnedYes
browse_allYes
attributionYes
total_matchingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / jobs / items / properties / pay / description
      Previous value: -"Stated pay; \"(estimate…)\" marks an estimate, not the listing rate."New value: +"Pay as the listing states it. Text ending in \"(estimate, not stated in the listing)\" is our estimate; \"(platform range, not this role's rate)\" is the range the platform posts for all its projects."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds value beyond them: result ordering ('highest match first'), a cap of 10, per-result rationale, and a privacy guarantee ('Nothing about the person is stored'). It does not cover freshness of the job data or whether the ranking considers all open roles, but the additions are meaningful.

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 tight sentences: what it does, when to use it, what it returns. Nothing is redundant and the core purpose is front-loaded.

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, the description needn't detail return shape, and it still summarizes count and ordering. Parameters and annotations are well covered, leaving only minor gaps such as result freshness and whether ranking is strict or fuzzy on the profile fields.

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 the schema. The description restates the matching dimensions and the USD currency of min_hourly_pay but adds no weighting, precedence, or fallback behavior beyond what the schema provides.

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 opens with a specific verb+resource ('Rank open AI training and AI evaluation roles') and enumerates the matching dimensions, so the tool's function is unambiguous. It does not explicitly name the sibling search_jobs to draw the contrast, relying instead on 'for one person' and 'by their profession, skills...' to imply the difference.

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?

'Use when the user describes their own background, e.g. "I am a nurse in Canada"' gives a clear trigger condition plus a concrete example. It stops short of naming alternatives (search_jobs) or stating when not to use it, so the routing is implied rather than explicit.

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