Vestige

Get target metadata

vestige_get_target

Read-only

Retrieve a registered target's metadata and which providers support it, so you can identify compatible analysis providers before inspecting an artifact.

Instructions

Get one registered target's metadata plus which providers support it.

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

Input Schema

Name	Required	Description	Default
`artifactId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 4, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that provider support is included; it says nothing about what happens for an unknown artifactId, error behavior, or how 'registered' targets relate to listing results.

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

Conciseness4/5

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

One sentence, front-loaded and free of redundant wording. It is arguably too terse rather than padded, but nothing is wasted.

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

Completeness2/5

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

For a lookup tool with an undocumented required parameter and no output schema, the description should identify the ID source and describe the returned metadata shape. As written it leaves key invocation details unstated.

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 coverage is 0%, so the description carries the full burden. It never mentions artifactId, its required nature, its minimum length, or where such an ID comes from (e.g., vestige_register_target or vestige_list_targets output).

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 a specific verb ('Get') and resource ('one registered target's metadata') and adds scope ('plus which providers support it'). It distinguishes itself reasonably from vestige_list_targets, though it doesn't name that sibling explicitly.

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 explicit when-to-use or when-not-to-use guidance and no named alternatives. The single-target scope implies it differs from vestige_list_targets, but the agent must infer that.

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

Deploy Server