Skip to main content
Glama

job_complete

Mark the job as completed. This sanitizes PII from the context and records a completion summary. Use when all tasks in the job are done.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoOmit it: the run's own job is used.
summaryNoBrief summary of what was accomplished
trace_idNoOnly for a session working an agent task DialogBrain handed to it: that task's Trace ID, which names the run's job and thread. Omit it inside an agent's own run.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / trace_id
      Added value: +{
      +  "description": "Only for a session working an agent task DialogBrain handed to it: that task's Trace ID, which names the run's job and thread. Omit it inside an agent's own run.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description adds the non-obvious disclosure that the call wipes PII from the context and writes a completion summary. Worth noting: erasing context data sits in mild tension with destructiveHint=false, but the behavior is disclosed rather than contradicted, so no contradiction flag. It does not mention that the call is non-idempotent, which annotations already supply.

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?

Three short sentences: action, side effects, then usage condition. It is front-loaded, has zero filler, and each sentence carries information the schema and annotations do not.

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 zero-required-parameter mutation with fully documented schema and no output schema, the description covers what the call does and what it changes. The only gap is what happens on a repeat call or after completion, which would matter for a non-idempotent operation.

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 100% and every parameter, including the optional job_id and trace_id fallbacks, carries a meaningful description in the schema itself. The description adds no parameter-level syntax or defaults beyond that, so the 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?

States a specific verb and resource ('Mark the job as completed') and adds the two effects that define the operation: PII sanitization and a recorded completion summary. It is distinct from the sibling job_escalate and job_update_context by implication, though it never names them explicitly.

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

Usage Guidelines4/5

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

'Use when all tasks in the job are done' gives a clear triggering condition, and the job_id/trace_id schema descriptions clarify which identifiers to omit. It stops short of explicit when-not guidance or routing to alternatives such as job_escalate, so it is clear but not exhaustive.

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.