Skip to main content
Glama

OpenTrain

Get an OpenTrain Job

opentrain_get_job
Read-onlyIdempotent

Read one OpenTrain job in full: pay, languages, countries, skills and the plain-text description. Use it after opentrain_search_jobs, or when someone shares an OpenTrain job link. Pass id, or url as the job page link (https://www.opentrain.ai/jobs/--/). A job that is closed or not public returns status "closed". Anonymous and read-only.

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

Input Schema

NameRequiredDescriptionDefault
idNoJob id from a search result.
urlNoJob page URL, https://www.opentrain.ai/jobs/<slug>--<id>/.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the description doesn't need to restate safety. It adds genuinely new behavior: closed or non-public jobs return status "closed", and access is anonymous. It does not mention rate limits or whether the full description is truncated for long postings.

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 ordered as purpose, usage trigger, parameter form, then edge-case outcome. No filler and the most decision-relevant information (what it returns, when to call it) comes first.

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?

An output schema exists, so return values need no explanation, and the description covers both parameters plus the closed-job outcome. The one gap is that neither parameter is required, yet the description doesn't say what happens if both id and url are omitted or disagree.

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 both parameters are already documented, including the URL pattern. The description only restates the same URL template and adds the minor hint that id comes from a search result, which is near the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read one OpenTrain job in full" gives a specific verb, an explicit cardinality constraint, and enumerates the returned fields (pay, languages, countries, skills, description). The contrast with opentrain_search_jobs (single record vs. discovery) is clear from the wording alone.

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?

It names the concrete trigger conditions: after opentrain_search_jobs, or when a user shares a job link. It never states an explicit when-not or describes what search should be used for instead, so the routing rule is implied rather than fully spelled out.

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