Skip to main content
Glama

Tolca: business verification (KYB)

pkg-meta

pkg_meta
Read-onlyIdempotent

Package metadata in one call, cheapest tier: latest and resolved version, license, first/last publish dates, weekly downloads, deprecation flag, install scripts, maintainers count. npm or PyPI. No vulnerability scan (see pkg-check for the full safe/caution/avoid verdict). Input: name, ecosystem (npm | PyPI), optional version. Costs $0.002 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/pkg-meta with an x402 client.

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_meta"
  }
}

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. Changed3 schema fields changed
    • addedInput schema / properties / ecosystem / description
      Added value: +"Package registry: npm or PyPI"
    • addedInput schema / properties / name / description
      Added value: +"Package name as published"
    • addedInput schema / properties / version / description
      Added value: +"Exact version; defaults to latest"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), and the description adds material behavioral context beyond them: the $0.002 USDC per-call cost, the x402 v2 payment scheme on Base or Solana, and the required PAYMENT-SIGNATURE header or direct POST to the endpoint. Those are exactly the operational facts an agent needs before invoking a paid remote tool, and nothing conflicts with the annotations.

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?

Front-loaded with the payoff (metadata returned, cheapest tier) before the exclusion, cost, and payment mechanics, and nearly every clause carries information. The one throwaway is the 'Input: name, ecosystem, optional version' sentence, which duplicates the schema verbatim. Dense but well ordered.

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?

There is no output schema, so the description's field enumeration is what tells the agent what comes back, and it does so comprehensively. Combined with the cost and payment instructions, an agent has everything needed to decide and to execute the call correctly.

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 the three parameters are already documented, including 'defaults to latest' for version and the npm/PyPI enum. The description's 'Input: name, ecosystem (npm | PyPI), optional version' mostly restates the schema without adding format constraints, validation rules, or edge-case behavior. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Package metadata in one call') and enumerates exactly what is returned: versions, license, publish dates, downloads, deprecation flag, install scripts, maintainer count. It also positions itself against the sibling 'pkg-check' as the non-scanning tier, so an agent can distinguish the two without opening either schema.

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?

Explicitly excludes the vulnerability-scan use case and redirects to pkg-check 'for the full safe/caution/avoid verdict', which is a real when-not/alternative rule. It also constrains ecosystem to npm or PyPI and notes version is optional. It stops short of stating the positive trigger (e.g., 'use when you only need cheap registry facts'), leaving that to inference from the field list.

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.