universal-brute-workpack

audit.ingest_report

Ingest a host-mediated worker report into the audit run directory to track task execution status and outputs.

Instructions

Ingest one host-mediated worker report into an audit runDir.

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": "audit.ingest_report"
  }
}

Input Schema

Name	Required	Description	Default
`output`	No
`report`	No
`runDir`	No
`status`	No
`taskId`	No
`attempt`	No
`workerId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Jun 30, 2026

TDQS

C2/5.0

Behavior2/5

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

No annotations are provided, and the description gives no details on side effects, idempotency, required state (e.g., does runDir need to exist?), or what happens on conflict. The term 'host-mediated' is undefined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise (one sentence) but omits essential information, making it under-specified rather than efficiently informative.

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

Completeness1/5

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

With 7 parameters, no schema descriptions, no output schema, and no annotations, the description is completely inadequate. Missing required fields, examples, return behavior, and error cases.

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

Parameters1/5

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

Schema description coverage is 0% and description does not explain any parameter's meaning or format. Agent must guess from parameter names alone, which is insufficient for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Ingest one host-mediated worker report into an audit runDir,' which identifies the verb and resources but uses jargon ('host-mediated worker report') and does not distinguish from sibling tools like audit.collect or audit.prepare.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as audit.collect or audit.run. No prerequisites, exclusions, or context provided.

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