Skip to main content
Glama

Remote Nomad Jobs

Get job details

get_job
Read-onlyIdempotent

Full details of one job: description, salary, benefits, experience level, dates, and its remotenomadjobs.com job page, where the application is made. Accepts the id from search_jobs or a remotenomadjobs.com job URL.

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": {
      "job": "<job>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesJob id (24 characters) or a remotenomadjobs.com job URL.

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds useful context by listing the detail fields returned and noting that the remotenomadjobs.com job page is 'where the application is made', which tells the agent the application step happens off-tool. It says nothing about behavior for an invalid or expired id.

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, both front-loaded with the payload description first and the input convention second. There is no filler or redundancy.

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 no output schema, the description carries the burden of describing the returned content and does so by enumerating the detail fields; annotations cover the safety profile. The one gap is error behavior for a bad or expired id, which is minor for a one-parameter getter.

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% and the schema already states 'Job id (24 characters) or a remotenomadjobs.com job URL'. The description restates the same id-or-URL acceptance without adding format, validation or fallback detail, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource ('Full details of one job') and enumerates the returned fields (description, salary, benefits, experience level, dates, job page), which clearly separates it from the sibling search_jobs, a list/search tool.

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 establishes the retrieval flow by saying the tool 'Accepts the id from search_jobs or a remotenomadjobs.com job URL', which tells the agent when this tool applies. It stops short of an explicit exclusion such as 'use search_jobs instead when you need to discover jobs', so the guidance is clear but not fully contrastive.

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