VERDICT

Overview Schema Source Related Servers Discussions Admin

audit_get_exec

Retrieve provenance records by execution ID to trace findings back to the exact tool execution that produced them, with an option to include archived raw output.

Instructions

Fetch a provenance record by exec_id so any finding can be traced to the exact tool execution that produced it. Optionally include a slice of the archived raw output.

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": {
      "exec_id": "<exec_id>"
    },
    "name": "audit_get_exec"
  }
}

Input Schema

Name	Required	Description	Default
`exec_id`	Yes
`include_raw`	No
`raw_max`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses optional raw output inclusion and mentions 'archived raw output', hinting at behavior. Does not mention error handling or rate limits, but for a simple fetch this is adequate.

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 sentences, front-loaded with purpose and followed by optional behavior. No superfluous words; earns its place.

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?

Given an output schema exists (not shown), description need not detail return values. It covers the core operation and optional behavior. Could mention provenance record structure, but output schema likely covers that.

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 description must add meaning. It mentions 'include a slice of the archived raw output' for include_raw and raw_max, but does not explain raw_max units (e.g., bytes/characters) or the exact format of exec_id.

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?

Description states verb 'Fetch' and resource 'provenance record by exec_id', and ties it to tracing findings to tool executions. It distinguishes from siblings implicitly (e.g., audit_list_execs lists all execs), but does not explicitly compare to alternatives.

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?

Implies use for provenance tracking ('so any finding can be traced'), but lacks explicit guidance on when to use this versus alternatives like audit_list_execs, and no when-not-to-use examples.

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