shapeless

Job brief

jobs_brief

Read-only

Retrieve compact context for resuming a conversation: recent messages, artifact inventory, post statuses, and web URL; use jobs_get for full transcript and jobs_continue to reply.

Instructions

Compact context for continuing a conversation: the last messages clipped, an artifact inventory, post statuses, and the web url. Use jobs_get for the full transcript, jobs_continue to reply. Needs the read 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": {
      "id": "<id>"
    },
    "name": "jobs_brief"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The job id.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`live`	Yes
`title`	Yes
`status`	Yes
`outputs`	Yes
`messages`	Yes
`artifacts`	Yes
`createdAt`	Yes
`createdBy`	Yes
`updatedAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.4Oct 13, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds a useful auth note ('Needs the read scope') and outlines the return content, but does not cover pagination, clipping thresholds, or error behavior. With annotations carrying the safety burden, a 3 is appropriate.

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 tightly packed sentences: the return contents come first, then routing alternates and the scope requirement. No filler and nothing redundant.

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

Completeness5/5

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

An output schema exists, so return values need not be re-explained, and the description nonetheless previews the brief's contents. Combined with annotations covering safety and the routing to siblings, an agent has everything needed to call this correctly.

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 the single 'id' parameter is documented in the schema as 'The job id.' The description adds nothing about id format or sourcing beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Compact context for continuing a conversation') and enumerates exactly what the brief contains (clipped last messages, artifact inventory, post statuses, web url). It explicitly names the sibling tools jobs_get and jobs_continue, so an agent can distinguish it without opening schemas.

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?

Routes the agent directly: use jobs_get for the full transcript and jobs_continue to reply, which frames this tool as the compact middle-ground. It also states the prerequisite ('Needs the read scope'), covering both alternative selection and access requirement.

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

Deploy Server