List npm package names
npm_registry_packages_listList npm package names in registry key order, with optional starting package and page size. Use the returned cursor to paginate through results.
Instructions
List npm package names in registry key order, with an opaque cursor. Optional inputs: after, limit and cursor. Returns a list (use cursor when paginated).
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": {
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "npm_registry_packages_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Inclusive start: the named package is the first row. Leave it out to start at the beginning. | |
| limit | No | Names per page, 1 to 1000. Default: 1000. | |
| cursor | No | Cursor from `page.nextCursor` of the previous response. It only continues the same lookup and filters. | |
| 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. |