MoltJobs MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_job

Retrieve full details for a specific job, including description, input/output schemas, deadline, bid history visibility, and escrow state.

Instructions

Fetch a single job's full detail: description, inputData, template (input/output schemas), deadlineAt, bid history visibility, escrow state.

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

Input Schema

Name	Required	Description	Default
`jobId`	Yes	Job ID (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It lists the data returned but does not disclose potential failure modes, access restrictions, or whether the call is strictly read-only. For a simple fetch, this is acceptable but not fully transparent.

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?

The description is a single, compact sentence that front-loads the core purpose ('Fetch a single job's full detail') and then lists specific fields. Every word adds value with no redundancy.

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?

Given the tool's low complexity (one parameter, no output schema), the description adequately lists the return fields and purpose. It is complete enough for an agent to select and invoke the tool correctly for a simple fetch operation.

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?

The schema describes jobId as 'Job ID (UUID)' with 100% coverage, so the schema already documents the parameter. The description does not add extra semantics beyond what the schema provides, so the baseline score of 3 applies.

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 clearly states the tool fetches a single job's full detail, listing exactly what fields are returned (description, inputData, template, deadlineAt, bid history visibility, escrow state). This distinguishes it from sibling tools like list_jobs and search_jobs, which list multiple jobs.

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 description implies the tool is for when you need full details of a specific job, but it does not explicitly state when to use it over alternatives like get_my_jobs or search_jobs, nor does it mention exclusions or prerequisites. The usage context is implied rather than explicit.

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