Skip to main content
Glama

AI training pay by kind of work

get_ai_training_pay
Read-onlyIdempotent

What AI training work pays per hour today, by kind of work: the median and the typical range (25th to 75th percentile) of the rates open roles advertise, with how many rates and platforms each figure comes from. A rate is shown only when at least three platforms advertise it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: figures describe open-role advertised rates, and a rate is suppressed unless at least three platforms advertise it, plus each figure carries its own sample count. This data-threshold disclosure is exactly the kind of context annotations cannot convey.

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?

Two sentences, no filler. The payload (what pays what, per kind of work) leads, and the qualifying details (percentile definition, sample counts, three-platform floor) follow. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carry the return-shape burden, and it does: it names the central statistic, the dispersion measure, the provenance counts, and the suppression rule. An agent knows what it will receive and how to caveat it without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema takes no parameters (additionalProperties: false), so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool is 4. No parameter meaning is missing.

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 (get) and resource (AI training pay), scopes it to 'by kind of work,' and enumerates the exact figures returned (median, 25th–75th percentile, sample counts). It is clearly distinct from search_ai_training_jobs in concept, but never names or contrasts the siblings explicitly, so it stops short of a 5.

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?

Usage is only implied: an agent can infer it should call this for current hourly pay benchmarks, but there is no explicit when-to-use, no precondition, and no routing away from get_ai_training_market or search_ai_training_jobs. With zero parameters the invocation is trivial, which keeps this at a viable 3 rather than lower.

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