Skip to main content
Glama
kongyo2

@kongyo2/npm-info-mcp-server

Check npm Package TypeScript Support

npm_package_types
Read-onlyIdempotent

Checks if an npm package includes TypeScript type definitions. Detects bundled types from types, typings, or exports fields and suggests @types/ package when missing.

Instructions

Check whether an npm package ships TypeScript type definitions.

Detects bundled types from three sources (in priority order):

  1. types field

  2. typings field

  3. exports map with a types condition (modern conditional exports)

Also checks for a DefinitelyTyped (@types/) companion package when no bundled types are found, and surfaces typesVersions (TS-version-specific type maps) when present.

Args:

  • package_name (string): The npm package name

  • version (string, optional): Specific version to check (defaults to latest)

Returns markdown with:

  • Whether bundled types are present and which field declared them

  • Type-definitions entry path

  • Number of subpaths typed via exports (when applicable)

  • Whether a typesVersions map is declared

  • Whether @types/ exists on DefinitelyTyped, plus its latest version

  • An install command when @types is needed

Examples:

  • "express" -> @types/express on DefinitelyTyped

  • "zod" -> Bundled types (TypeScript-first library)

  • "react" -> Bundled types via exports/types condition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNoSpecific version to check (default: latest)
package_nameYesnpm package name
Behavior5/5

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

Annotations already mark it as readOnly, idempotent, and non-destructive. The description adds significant behavioral detail: priority order of type sources, DefinitelyTyped fallback, typesVersions handling, and return format specifics. No contradiction with 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?

The description is well-structured with bullet points and example cases. It is somewhat lengthy but each sentence adds value. Front-loads the main action effectively.

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 no output schema, the description fully explains the return markdown fields. Covers all aspects: bundled types, DefinitelyTyped check, typesVersions, and install command. Sufficient for the tool's complexity.

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 both parameters described. The description repeats the parameter names and defaults but adds no new semantic detail. 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?

The title and description clearly state the tool checks for TypeScript type definitions in npm packages. It specifies three bundled-type sources, DefinitelyTyped check, and typesVersions. This distinguishes it from siblings like npm_package_info or npm_package_dependencies.

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 provides clear context for when to use (to check TypeScript support). It includes examples showing expected results for different packages. However, it does not explicitly state when not to use or mention sibling tool alternatives.

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/kongyo2/npm-info'

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