Skip to main content
Glama

job_evidence

Retrieves the exact lines a delegated job cited for each contract constraint, with surrounding context, so you can inspect focused evidence instead of reading the whole diff.

Instructions

The lines the executor cited for each contract constraint, with context lines around them, read from the files as they are now. This is the focused inspection of a delegated job: a few dozen lines instead of the whole diff. It satisfies the inspection asked by job_feedback when the job is verified by checks that failed before the work and every constraint has checked evidence; in any other case it says so and job_diff is still needed. Lines that no constraint cites are covered only by the verify commands: use job_diff when you want to read them.

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_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
contextNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.6.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does much of it: it discloses that lines are 'read from the files as they are now' (live re-read, not the job-time snapshot), that the tool may decline with a message when preconditions are unmet, and that uncited lines are outside its coverage. It stops short of explicitly declaring the operation read-only or describing failure on an invalid job_id.

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?

The return shape is front-loaded, followed by the use condition and the boundary, in a logical order. It is dense but nearly every sentence adds a decision-relevant fact; the closing sentence about uncited lines slightly restates the job_diff boundary already established.

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 two-parameter read with an output schema, the description covers what is returned, the precondition for usefulness, the fallback, and the coverage boundary. The only meaningful omission is error behavior for a bad or unknown job_id, which the output schema does not cover.

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 coverage is 0%, so the description must compensate. It explains the `context` parameter's meaning ('`context` lines around them') but says nothing about its default or bounds, and `job_id` is only implicitly identified. It adds real meaning for one of two parameters but leaves the other to inference.

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 opens with a concrete verb+resource: 'The lines the executor cited for each contract constraint, with `context` lines around them, read from the files as they are now.' It then frames the tool as 'the focused inspection of a delegated job: a few dozen lines instead of the whole diff,' which directly separates it from the sibling job_diff.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is stated as an explicit condition: it 'satisfies the inspection asked by job_feedback when the job is verified by checks that failed before the work and every constraint has checked evidence; in any other case it says so and job_diff is still needed.' It names the alternative (job_diff) and the condition that selects it, plus the exclusion for uncited lines.

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