Skip to main content
Glama

Get Job Tool

get-job
Read-only

Returns one authorized job using bounded customer, schedule, status, and technician fields; service addresses, notes, and amounts are excluded. Use to get job in the connected business. Returns job, scope.

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_idYesJob ID returned by search-jobs or jobs-today.

Output Schema

NameRequiredDescriptionDefault
jobYesJob data returned by the authorized safe projection.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "job_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "job": {
      +      "description": "Job data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "job",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety and locality are covered by structured data. The description does add genuine value beyond them: the field allowlist/denylist (addresses, notes, amounts excluded) and the word 'authorized,' which signals permission-scoped results. A 3 rather than higher because the exclusion list reads as a field inventory rather than an explanation of what the caller loses or why it matters.

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?

Two compact sentences with the most important scoping (single authorized job, field boundaries) front-loaded. The middle sentence 'Use to get job in the connected business' is filler that contributes almost nothing, and the trailing 'Returns job, scope' is terse to the point of ambiguity.

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 an output schema present, the description needn't explain return values, and the rich annotations cover the safety profile. The field-boundary statement fills the main remaining gap for a single-record fetch tool, though a note on behavior for an invalid or unauthorized job_id would round it out.

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 job_id is documented with its source tools, so the schema does the heavy lifting. The description adds no format, type, or constraint information about job_id. Baseline 3 applies when the schema fully documents the single parameter.

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 -- 'Returns one authorized job' -- and scopes it to 'bounded customer, schedule, status, and technician fields,' which separates it from sibling listing tools like jobs-today by emphasizing a single record. It also names what is excluded (service addresses, notes, amounts), though it never explicitly contrasts itself with search-jobs or jobs-today by name.

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?

'Use to get job in the connected business' only restates the purpose rather than giving a real condition for selection. The ID-provenance hint lives in the schema ('returned by search-jobs or jobs-today'), not the description, so the when-to-use-vs-alternatives guidance is only implied. An agent can infer it needs a job_id already in hand, but nothing in the description states exclusions or prerequisites.

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