Skip to main content
Glama
Sign In

aitrainer.work AI training jobs

by work.aitrainer
OverviewDiscussionsAdmin

Get one AI training job

get_job
Read-onlyIdempotent

Full details of one role: description, requirements, pay and its source, hours, interview, countries.

Input Schema

NameRequiredDescriptionDefault
slugYesJob slug from search_jobs results.
platformYesPlatform key from search_jobs results.

Output Schema

NameRequiredDescriptionDefault
payYesPay 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.
urlYesThe role page on aitrainer.work, with the full listing and the application link.
openYes
slugYes
titleYes
platformYes
attributionYes
match_reasonsNo
platform_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / 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. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "type": "string"
+    },
+    "match_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "open": {
+      "type": "boolean"
+    },
+    "pay": {
+      "description": "Stated pay; \"(estimate…)\" marks an estimate, not the listing rate.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "platform": {
+      "type": "string"
+    },
+    "platform_name": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "description": "The role page on aitrainer.work, with the full listing and the application link.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "platform",
+    "platform_name",
+    "slug",
+    "pay",
+    "url",
+    "open",
+    "attribution"
+  ],
+  "type": "object"
+}
  3. 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, closed-world and non-destructive, so the safety profile is covered. The description adds the shape of the payload but says nothing about behavior beyond it — no handling of a missing slug/platform, no cross-platform behavior, no note on freshness of pay data despite mentioning 'its source'.

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?

A single front-loaded sentence with no filler. The trailing field enumeration is partly redundant with the output schema, but it still orients the agent quickly, so the slight redundancy is tolerable.

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, real annotations, and full parameter coverage, the description only needs to frame scope — which it does, including the useful 'pay and its source' nuance. The remaining gap is failure behavior for an unknown slug/platform.

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 both parameters explicitly state they come from search_jobs results, so the schema carries the semantics. The description adds nothing about slug/platform format or pairing rules, making this baseline territory.

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 names a specific retrieval action ('Full details of one role') and enumerates the payload (description, requirements, pay/source, hours, interview, countries), which is far more informative than the title alone. It implicitly distinguishes itself from search_jobs by retrieving a single item's full detail, but never names the sibling, and it drifts between 'role' and the tool's 'job' terminology.

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 this is the follow-up call to search_jobs for a single record. There is no explicit when-to-use statement, no pointer to get_pay_stats or get_interview_prep as alternatives for the pay/interview facets it mentions, and no note that both platform and slug must come from a prior search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All aitrainer.work AI training jobs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources