Skip to main content
Glama

job_diff

Show the unified diff of changes made by a delegated job, optionally limited to one file, so you can review exactly what was modified.

Instructions

Unified diff of what a delegated job changed (one file if path is given).

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

Input Schema

NameRequiredDescriptionDefault
pathNo
job_idYes
max_linesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape (a unified diff) and the path-scoping behavior, but says nothing about whether the diff is truncated, what the job-state prerequisites are, or how max_lines affects output — a notable gap for a read tool with a silent 200-line default.

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?

A single front-loaded sentence with no filler, and the conditional scoping detail is placed where it is immediately useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return format need not be described. However, with zero annotation coverage and undocumented max_lines/job_id semantics, the definition leaves real gaps for an agent invoking it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters. The description only explains 'path' (narrowing to a single file); neither the required 'job_id' nor 'max_lines' gets any meaning added, leaving the agent to infer truncation behavior from the parameter name alone.

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 gives a specific verb+resource pair ('Unified diff') scoped to a specific object ('what a delegated job changed'), which clearly separates it from status- or rollback-style siblings. It does not explicitly name an alternative tool, but the resource is unambiguous.

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 only implied: an agent can infer it should call this to inspect a job's changes. There is no explicit when-to-use statement, no when-not, and no pointer to siblings like job_status for non-diff inspection.

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