nuvio_list_profilesRetrieve all Nuvio profiles with index, name, avatar, flags, and PIN lock state. Use this to review account profiles and their security settings.
List all profiles (index 1..6, name, avatar, flags, PIN lock state).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds concrete behavioral detail by specifying the fixed index range 1..6 and the exact data fields returned. This gives an agent useful expectations beyond the structured hints.
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?
A single, front-loaded sentence conveys the operation, scope, and output fields with no filler. Every part earns its place.
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?
For a parameterless read-only list tool with no output schema, the description completely covers what an agent needs to know: what it lists, the index range, and which fields are included. No critical information is missing.
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 tool has zero parameters, so there are no parameter semantics to clarify. The description still adds value by describing what data the no-argument call returns.
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 names the exact verb ('List'), the resource ('all profiles'), and enumerates the returned fields: index 1..6, name, avatar, flags, and PIN lock state. This clearly distinguishes it from profile mutation tools like nuvio_create_profile or nuvio_delete_profile.
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 read-only enumeration nature makes its basic use clear, and the description implies it is the appropriate tool for inspecting all profiles rather than modifying them. However, it does not explicitly state when to choose this over sibling profile tools or mention any prerequisites or exclusion cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.