Vestige

Export analysis report

vestige_export_report

Read-only

Export a deterministic Markdown or JSON report for an authorized artifact into the Vestige workspace and return its absolute file path.

Instructions

Export a deterministic markdown or JSON report for a target into the Vestige workspace and return its absolute path.

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": {
      "artifactId": "<artifactId>"
    },
    "name": "vestige_export_report"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No		markdown
`artifactId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely useful behavior beyond them: the output is deterministic, the format is selectable, and the call returns an absolute path. It does not disclose where exactly in the workspace the file lands, whether an existing file at that path is overwritten, or what happens if the artifact does not exist.

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?

A single front-loaded sentence that goes verb, format, scope, destination, return value, with no filler. Every clause carries information.

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

Completeness3/5

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

For a two-parameter tool with no output schema, the description does supply the return value (absolute path) and format options, which is the right coverage for a simple tool. However, the artifactId-versus-'target' ambiguity and the undisclosed overwrite/location behavior leave real gaps for an agent that must call this correctly the first time.

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

Parameters2/5

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

With 0% schema description coverage, the description carries the full burden, and it only partly does so: it explains the markdown/JSON choice, which maps to the format enum, but adds nothing about artifactId (min length 4, required). Worse, it refers to exporting 'for a target' while the actual required parameter is artifactId, a terminology mismatch that could lead an agent to pass a target 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?

States a specific verb (Export) plus the resource (a deterministic markdown or JSON report) and the destination (the Vestige workspace), and even discloses the return value (absolute path). It does not distinguish itself from siblings such as vestige_analyze or vestige_get_evidence, so an agent must infer the sequencing on its own.

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?

Usage is only implied: the parameters suggest exporting a report for an existing artifact after analysis, but the description never says when to call this rather than vestige_analyze, vestige_list_findings, or vestige_get_evidence. There are no prerequisites or exclusions stated.

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

Deploy Server