Get npm package full registry document
npm_package_details_getFetch an npm package's full registry document, including every version, README, star count, and timestamps, by passing the package name.
Instructions
Get npm package registry document with every version, README, stars and timestamps. Requires name.
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>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "npm_package_details_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Required. npm package name, e.g. `express`, `lodash.merge`, `@types/node` or `--file--1`. Names are case-sensitive (`Express` is a different package) and keep legacy punctuation such as a leading `-`. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |