pm_listRetrieve your private message conversations from Nexus Mods, showing IDs, titles, participants, message previews, and unread status. Requires an active logged-in session.
List your private-message conversations (forum messenger): id, title, participants, last message snippet, unread flag. Needs a logged-in web session.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds useful behavioral context by specifying the need for a logged-in session and enumerating the return fields. It does not contradict annotations and provides value beyond the structured metadata.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. It front-loads the primary purpose and return fields, then adds the session requirement. Every word contributes to understanding the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the essential aspects: what it lists, the return fields, and the session requirement. However, it omits any mention of the page parameter or how pagination works. Given the tool's simplicity and the presence of an output-less schema, this is a minor gap but not critical for basic usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, meaning the page parameter is completely undocumented in the schema. The description does not mention pagination or explain the page parameter at all, leaving the agent to infer its purpose from the name and default value. This is a significant gap for a tool with a pagination parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'List' and the resource 'private-message conversations', specifying the exact fields returned (id, title, participants, last message snippet, unread flag). It distinguishes itself from sibling pm_* tools (pm_send, pm_reply, pm_leave, pm_read) by focusing on listing conversations, making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes a prerequisite (logged-in web session) but does not explicitly mention when to use this tool versus alternatives like pm_read or pm_send. The distinction is implied by the action of listing, but there is no direct guidance on selection criteria or exclusion conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.