Skip to main content
Glama

Get a job

jobs_get
Read-onlyIdempotent

One job: brief, criteria, attached context (full text once accepted), files (read them with files_get), the thread, deliverables, audit trail and ratings. After a job closes the contractor sees only its summary, trail and ratings.

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

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
jobIdYesJob id (from jobs_list or jobs_post)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is largely covered. The description adds genuinely non-obvious behavior: full context text is only available once the job is accepted, and after closure the contractor sees only summary, trail and ratings. That visibility asymmetry is real context an agent could not get from the schema.

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, front-loaded with the resource, then a dense but purposeful enumeration of return contents followed by a critical visibility caveat. No filler or restatement of the title.

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, describing what comes back is exactly the right compensation, and it does so concretely, including the files hand-off to files_get. A note on what an inaccessible or closed job returns for non-contractor roles would have closed the remaining gap.

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 both parameters (jobId and the conditional `as` handle) are documented in the schema itself. The description adds nothing about parameter format or the conditional nature of `as`, so baseline 3 applies.

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?

"One job:" plus an enumeration of what the record contains (brief, criteria, context, files, thread, deliverables, trail, ratings) makes the verb+resource unmistakable and separates it from the list-style siblings. It stops short of naming jobs_list as the alternative, so it is clear but not fully differentiated.

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: you fetch one job when you have a jobId. The description does give one useful routing instruction, telling the agent to read attached files with files_get rather than expecting their contents inline. There is no explicit when-not guidance or named alternative for multi-job browsing.

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