devtools-mcp

Query Npm Version

query_npm_version

查询 npm 包的最新版本信息。输入 npm 包名（如 react、vue、express、@vue/cli），返回最新版本号 latest_version、该版本发布时间 published_at（UTC ISO 8601）、包描述 description、开源协议 license，以及主页/仓库地址等。数据源优先官方 registry.npmjs.org，失败自动兜底淘宝镜像 registry.npmmirror.com（国内更快）。包不存在返回明确的 404 提示。网络 I/O 走线程池不阻塞事件循环。

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": {
      "package": "<package>"
    },
    "name": "query_npm_version"
  }
}

Input Schema

Name	Required	Description	Default
`package`	Yes	npm 包名，如 "react"、"vue"、"express"、"@vue/cli"

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / package / description

Added value: +"npm 包名，如 \"react\"、\"vue\"、\"express\"、\"@vue/cli\""

removedInput schema / properties / package / title
```
Removed value: -"Package"
```

removedInput schema / title

Removed value: -"query_npm_versionArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedSep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and mostly delivers: it discloses the primary source (registry.npmjs.org), an automatic fallback to registry.npmmirror.com with a performance rationale, explicit 404 behavior for missing packages, and that network I/O runs on a thread pool so it won't block the event loop. Rate limits, caching, and whether fallback is silent are left unstated.

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 purpose, then return fields, then data source and error behavior—a sensible order with no filler. The thread-pool sentence is marginally useful but slightly off-topic for an agent deciding whether to call it.

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?

For a one-parameter lookup with an output schema and no annotations, the description covers the failure mode, the source-of-truth and fallback, and the return fields. What remains missing (caching, rate limits) is minor relative to the tool's simplicity.

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?

One parameter at 100% schema coverage means the schema already documents 'package', and the description's examples duplicate the schema's own. It adds only the scoped-package form (@vue/cli), which is also in the schema, so baseline 3 is right.

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 and resource ('查询 npm 包的最新版本信息') and enumerates exactly what comes back (latest_version, published_at, description, license, homepage/repo). That is far more specific than the sibling utilities (convert_unit, generate_uuid) and leaves no ambiguity about what the tool does.

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 input examples (react, vue, express, @vue/cli), which show the accepted package-name forms, but the description never states when to reach for this tool or when not to. No sibling overlaps in practice, so the gap is small but real.

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

All devtools-mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.