Skip to main content
Glama

AI Training Jobs

Pay for a field and country

pay_stats
Read-onlyIdempotent

What AI training jobs pay, from live listings that state an hourly rate: 25th percentile, median, 75th and 90th percentile of top rates, with the platforms hiring most. Optionally for one field and/or one country (listings that name the country or say worldwide).

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": "pay_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNoField of expertise: software (Engineers, data scientists, ML people); medicine (Physicians, nurses, dentists, clinicians); science (Physicists, chemists, biologists, engineers); math (Mathematicians, statisticians, theorem provers); finance (Analysts, accountants, bankers, consultants); law (Attorneys, paralegals, compliance experts); language (Native speakers, translators, linguists); audio (Voice actors, transcribers, recorders); writing (Writers, editors, copywriters); design (Designers, illustrators, artists, musicians); humanities (Teachers, professors, historians, social scientists); general (Evaluators and raters, often no degree needed).
countryNoWhere the person lives: a country name, slug or ISO code (e.g. "India", "united-states", "PH"). "any" turns the filter off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond that: the data comes only from listings that state an hourly rate, percentiles are computed on top rates, and country filtering includes listings that say "worldwide." That last point is a genuinely useful filter-semantics disclosure, but return shape and sample size are still unstated.

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, front-loaded with the core statistic definition before the optional filtering caveat. Dense but no wasted clauses; the percentile stack is a little packed on first read.

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 only two optional params and full annotation coverage, the description is nearly sufficient — it says what is computed (percentiles of top rates) and that platform counts are included. Without an output schema, it could go further on the actual response shape (e.g., whether platform counts are ordered pairs), but the qualitative picture is complete.

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 100% and the field enum is exhaustively documented, so the baseline is 3. The description does add marginal meaning — that both filters are optional and combinable, and that the country filter also catches "worldwide" listings — but it largely restates schema-level facts.

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 resource and computation: percentile pay rates (25th/median/75th/90th of top rates) for AI training jobs, plus top hiring platforms. That is clearly an aggregate/statistics tool, distinguishable from siblings like search_jobs or get_job, though no sibling is named explicitly.

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?

"Optionally for one field and/or one country" tells the agent the filters are optional and combinable, implying a default all-fields/all-countries query. However, there is no explicit guidance on when to use this versus search_jobs or get_job, and no stated prerequisitives.

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