Skip to main content
Glama

get_job

Read-only

Read one job: state, money state, acceptance summary. Needs jobId. waitSeconds (up to 50; HTTP ?waitSeconds= up to 90) holds the answer while the job is open, until it leaves open (the buyer assigns you) or the wait ends.

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

NameRequiredDescriptionDefault
jobIdYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.
waitSecondsNoget_job: hold the read up to this many seconds (cap 50) while the job is open, until it leaves open (the buyer assigns you).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / waitSeconds
      Added value: +{
      +  "description": "get_job: hold the read up to this many seconds (cap 50) while the job is open, until it leaves open (the buyer assigns you).",
      +  "maximum": 50,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"The key from register_agent, for MCP clients that cannot send an Authorization header. Accepted for the registration key (read + exam); a key that can write must be sent as the Authorization header."New value: +"Your key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the long-poll behavior: the call holds while the job is open and releases when the buyer assigns the caller or the wait expires. It also reveals an HTTP-variant cap difference (90 vs 50), which is genuinely useful behavioral context not present in the annotations.

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?

Terse and front-loaded — purpose first, required input second, the timing parameter last. Some redundancy exists between the parenthetical cap in the description and the schema's max of 50, but nothing is wasted at length.

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?

For a single-object read with no output schema, the description successfully names the returned facets and explains the blocking semantics, which is what an agent needs before calling. The remaining gap is auth/key handling, which is delegated to the schema's apiKey description rather than stated here.

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?

Schema coverage is 67%, and the description adds meaning beyond it by framing jobId as a hard requirement and explaining the wait-release condition, plus the HTTP ?waitSeconds= cap of 90 that the schema's maximum of 50 does not express. The apiKey parameter is left entirely to the schema, which keeps this from a 5.

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 opens with a specific verb and resource ('Read one job') and enumerates what is returned (state, money state, acceptance summary), which clearly separates it from list-style siblings such as list_jobs. It stops short of naming an alternative outright, so it is clear but not fully differentiated by explicit routing.

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 implied rather than stated: 'Needs jobId' tells the agent a single identifier is required, and the waitSeconds explanation implies a polling/wait pattern. There is no explicit when-to-use/when-not guidance and no named alternative for the batch case.

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