Skip to main content
Glama

Tolca: business verification (KYB)

Package safety check (npm / PyPI)

pkg_check
Read-onlyIdempotent

npm dependency risk and PyPI package safety check: is this package safe to install? One call, one verdict: safe / caution / avoid, with a score, concrete reasons (known vulnerabilities from OSV, deprecation, abandonment, adoption, install scripts, typosquat signals) and a one-line recommendation. Input: name, ecosystem (npm | PyPI), optional version. Free over MCP (100/day shared quota); unlimited via x402 at https://tolca.tonbot.ca/v1/pkg-check ($0.003).

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": {
      "name": "<name>",
      "ecosystem": "<ecosystem>"
    },
    "name": "pkg_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name as published
versionNoExact version; defaults to latest
ecosystemYesPackage registry: npm or PyPI

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ecosystem / description
      Added value: +"Package registry: npm or PyPI"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses output shape (verdict, score, reasons, one-line recommendation), evidence sources (OSV vulnerabilities, deprecation, abandonment, adoption, install scripts, typosquat signals), and rate/cost constraints (100/day shared quota, x402 pricing). That is exactly the operational context an agent needs before calling a read-only external check.

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?

The description is front-loaded with the core purpose and verdict model, then evidence sources, then quota/pricing. It is dense but each clause carries information; the endpoint URL and price are useful but slightly promotional in an otherwise tight definition.

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?

With no output schema, the description compensates by explaining the return verdict, score, reasons, and recommendation. Combined with quota and evidence-source disclosure, an agent has everything needed to decide to call it and interpret the result.

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 description coverage is 100%, so all three parameters are already documented, including the enum and the 'defaults to latest' behavior for version. The description's 'Input: name, ecosystem (npm | PyPI), optional version' restates the schema without adding format or naming nuance.

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 names a specific verb and resource ('npm dependency risk and PyPI package safety check') and frames the outcome precisely as 'safe / caution / avoid' with a score and reasons. It is immediately distinguishable from a metadata lookup sibling like pkg_meta, though it does not name siblings explicitly.

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 use case is clear ('is this package safe to install?') and the description adds operating context: a shared free quota of 100/day and a paid unlimited path. It does not state exclusions or name alternative tools for when a safety verdict is not what the agent needs, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.