Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaRelated ServersScoreDiscussions
Python

Package Integrity Verify

verify
Read-onlyIdempotent

Checks SHA-256 hashes and SLSA provenance attestations for packages from npm or PyPI to confirm integrity and source repository claims.

Instructions

Verify package integrity and SLSA provenance against registries.

    Checks SHA-256/SRI hashes against npm/PyPI registries and looks up
    SLSA build provenance attestations to confirm the package was built
    from its claimed source repository.

    Returns:
        JSON with integrity verification (hash match, expected vs actual)
        and provenance status (SLSA level, source repo, build trigger).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPackage name with optional version, e.g. 'express@4.18.2' or 'requests==2.31.0'.
ecosystemNoPackage ecosystem: 'npm' or 'pypi'.npm

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior5/5

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

Annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) are consistent and the description adds valuable context: it checks SHA-256/SRI hashes against npm/PyPI and looks up SLSA provenance. No contradictions.

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?

The description is concise, front-loaded with the core purpose, and structured into clear sections. Every sentence adds value without redundancy.

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 the tool's simplicity (2 parameters, annotations, output schema), the description covers key aspects: what it checks (hashes, provenance), how (against registries), and the return format. Minor omission: no mention of error handling or edge cases, but overall sufficient.

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 100% with descriptions for both parameters. The description does not add significant meaning beyond the schema, though it hints at the return format. Baseline 3 applies.

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?

The description clearly states it verifies package integrity and SLSA provenance, specifying the verb 'verify', the resources (package integrity, SLSA provenance), and the scope (against registries). It distinguishes from siblings like 'check' and 'scan' by focusing on integrity and provenance.

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?

The description implies usage for verifying package integrity and provenance but provides no explicit guidance on when to use this tool versus alternatives like 'registry_lookup' or 'skill_verify'. It lacks 'when not to use' or prerequisite information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server