package-truth

Check a dependency manifest

check_manifest

Read-onlyIdempotent

Check a manifest file's dependencies for existence, deprecation, known vulnerabilities, and license issues before installation. Get a verdict for every dependency and a prioritized list of problems.

Instructions

Checks every dependency in a manifest file's text (package.json, requirements*.txt, pyproject.toml, Cargo.toml, go.mod, Gemfile, *.csproj, pom.xml). Pinned versions are checked exactly; ranges at the version an install would pick today. Problems are listed first.

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": {
      "filename": "<filename>",
      "content": "<content>"
    },
    "name": "check_manifest"
  }
}

Input Schema

Name	Required	Description	Default
`content`	Yes	The file's full text
`filename`	Yes	File name, e.g. package.json

Output Schema

Name	Required	Description	Default
`counts`	Yes
`results`	Yes
`skipped`	No
`ecosystem`	Yes
`truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the description need not restate those. It adds useful behavioral detail beyond annotations: exact pins are checked exactly, ranges are resolved to today's install-pick version, and problems are listed first.

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 tight, front-loaded sentences: the first names the action and scope, the second states version-resolution semantics and output ordering. Every sentence earns its place with no filler or repetition of the schema.

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

Completeness5/5

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

For a two-parameter read-only tool with a 100%-documented schema, rich annotations, and an output schema, the description provides everything needed to call it correctly: input expectations, version-checking semantics, scope, and result ordering. No critical behavioral gap remains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds value by listing the accepted manifest filename patterns (package.json, requirements*.txt, pyproject.toml, etc.) and clarifying that content is the full file text. This goes beyond the schema's generic 'e.g. package.json' example.

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?

The description clearly states the tool checks every dependency in a manifest file's text and enumerates supported manifest formats, giving a specific verb and resource. It does not explicitly distinguish itself from the sibling check_packages, though the 'manifest file's text' framing makes the scope inferable.

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?

There is no explicit guidance about when to use this tool versus get_advisories or check_packages. The supported-format list implies it is for manifest-file inputs, but no alternative is named or excluded, leaving the agent to infer the decision.

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

Deploy Server