Skip to main content
Glama

Marketplace Trust Check

marketplace_check
Read-onlyIdempotent

Check pre-install trust of an MCP package by querying npm or PyPI registry and cross-referencing threat intelligence for CVE status, download count, and registry verification.

Instructions

Pre-install trust check for an MCP server package.

    Queries the package registry (npm or PyPI) for metadata and
    cross-references against the agent-bom MCP threat intelligence registry.
    Returns trust signals including download count, CVE status, and
    registry verification.

    Args:
        package: Package name to check.
        ecosystem: 'npm' or 'pypi'. Defaults to 'npm'.

    Returns:
        JSON with name, version, ecosystem, cve_count, download_count,
        registry_verified, and trust_signals.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPackage name, e.g. 'express', 'langchain'.
ecosystemNoPackage ecosystem: 'npm' or 'pypi'.npm

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by detailing the sources (npm/PyPI, threat intel registry) and the fields returned, expanding on what the agent can expect.

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 and well-structured, starting with a clear one-line summary, followed by a paragraph of detail, then structured Args and Returns 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.

Completeness5/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, output schema provided), the description fully covers the purpose, inputs, outputs, and sources. No missing information for an agent to decide whether to invoke it.

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?

The input schema covers both parameters with descriptions (100% coverage). The description adds examples ('express', 'langchain') and specifies the default for ecosystem, providing additional clarity beyond the schema.

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 performs a pre-install trust check for MCP server packages, querying npm/PyPI and cross-referencing threat intelligence. It distinguishes itself from siblings like 'registry_lookup' by adding trust signals, making the purpose very specific.

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 implies usage before installing a package through 'Pre-install trust check', but does not explicitly state when not to use it or provide alternatives. The context is clear enough for an agent to infer appropriate usage.

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