Skip to main content
Glama

Pre-Flight EVM Tx-Simulate, Allowance Firewall & Rebalance MCP

Verify npm or PyPI Package Against AI Hallucination & Slopsquatting

verify_package_anti_hallucination
Read-onlyIdempotent

Checks live npm and PyPI registries to block nonexistent hallucinated package names and flag newly registered slopsquatting traps (<14 days old).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_package_anti_hallucination"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemNo'npm' or 'pypi'
packageNameNoPackage name to verify before installation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds useful behavioral detail beyond that: it checks live registries and uses a specific 14-day age threshold to flag slopsquatting traps. It does not explain how blocking versus flagging is surfaced in the response, which prevents a higher score.

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 definition is a single front-loaded sentence with no filler. It identifies the registries, the hallucination check, the slopsquatting check, and the age threshold without repetition.

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?

This is a simple two-parameter verification tool with full schema coverage and annotations covering safety and idempotency. The description is nearly complete, but because there is no output schema, it could more clearly state what a successful verification versus a blocked or flagged result looks like.

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 both parameters are already documented in the schema. The description mentions npm and PyPI as the registry targets and references package names, but it adds no format, casing, scoping, or validation details beyond what the schema already provides.

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 uses a specific verb and resource: it checks live npm and PyPI registries for nonexistent hallucinated package names and newly registered slopsquatting traps. It is immediately distinguishable from the blockchain-related sibling tools, whose names imply entirely different resources.

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?

Usage is implied by the purpose ('block nonexistent hallucinated package names' and 'flag newly registered slopsquatting traps') and by the schema note that the package name is verified before installation. However, the description does not explicitly say when to call this tool, when not to, or name any alternative verification approaches.

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.