Skip to main content
Glama

Nectar Jobs

Get one job in full

get_job
Read-onlyIdempotent

Fetch a single job's full details, including its description and any duplicate postings of the same role on other sources.

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_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 behavior, so the safety profile is covered. The description adds real value by disclosing that results include duplicate postings of the same role from other sources — a non-obvious aggregation behavior. It does not address what happens if job_id does not exist, which is the main remaining gap.

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 efficient sentence that front-loads the action and then qualifies the payload. No filler, though the phrasing 'including its description and any duplicate postings' is slightly dense.

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 a one-parameter read tool requires little else. The definition covers what is fetched and that cross-source duplicates are bundled in; only identifier provenance and not-found behavior are absent.

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?

Only one parameter, and its name job_id is self-explanatory for a job-lookup tool; the description confirms the tool operates on a single job. Schema description coverage is 0%, so the description could have said where job_ids come from (e.g., search results), but the semantic gap is small.

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 and resource ('Fetch a single job's full details') and clarifies scope by naming what is included (description text plus duplicate postings from other sources). It is distinguishable from siblings by being a single-record retrieval, though it never names search_jobs or find_similar_jobs 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?

The word 'single' implies this is the follow-up call after a list/search, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that search_jobs precedes this call.

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