Vestige

Start analysis job

vestige_analyze

Read-only

Starts an asynchronous analysis job on a registered software artifact and returns a jobId for polling status. Use it to inspect JavaScript, TypeScript, or native binaries for verifiable, evidence-linked technical reporting.

Instructions

Start an asynchronous analysis job on a registered target. Returns a jobId immediately; poll vestige_job_status. Progress notifications are sent when the client supplies a progressToken in _meta.

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_analyze"
  }
}

Input Schema

Name	Required	Description	Default
`provider`	No
`artifactId`	Yes
`capabilities`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=false), the description discloses the asynchronous execution model, that the call returns immediately with a jobId rather than results, the polling pattern, and the progressToken/_meta mechanism for notifications — substantial behavioral context. Minor tension: annotations declare readOnlyHint=true while the tool 'starts a job', which may create server-side job state; this is unaddressed, as are failure modes and idempotency of repeated starts.

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, front-loaded with what the tool does and what it returns, followed by the follow-up action and the notification detail. Every sentence carries distinct information and nothing is padded or repeated from the schema.

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 an async job-launch tool with no output schema, the description adequately covers the return value (jobId) and the continuation path (poll or receive notifications). However, it leaves the two optional parameters unexplained and does not cover error behavior, job lifetime, or how a started job relates to vestige_job_cancel, so it is only minimally sufficient.

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?

Schema description coverage is 0% for 3 parameters, so the description carries the full burden and fails to meet it. Only 'registered target' loosely maps to the required artifactId; the optional 'provider' and especially 'capabilities' (an array up to 20 items) are never mentioned, leaving their meaning, defaults, and effect on the analysis completely undocumented.

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 ('Start an asynchronous analysis job on a registered target') and immediately pins down the return contract ('Returns a jobId immediately'). It also routes the agent away from this tool for follow-up work by naming vestige_job_status as the polling sibling, so it is distinguishable without opening any schema.

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?

The description gives a clear usage sequence: call this to start, then poll vestige_job_status, and supply a progressToken in _meta if the client wants push notifications. 'On a registered target' implies the prerequisite of prior registration, though it never states this explicitly and does not mention other alternatives such as vestige_job_cancel once the job is running.

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

Deploy Server