romm-mcp

Overview Schema Source Related Servers Discussions Admin

list_users

Read-onlyIdempotent

Retrieve minimal user identity details needed for subsequent API calls, excluding email, roles, OAuth scopes, and UI/device settings.

Instructions

List minimal user identity needed for follow-up calls; email, roles, OAuth scopes and UI/device settings are excluded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_users"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`limit`	No
`total`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context by stating the response is intentionally minimal and enumerating excluded fields, which helps set expectations beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the primary purpose front-loaded, followed by a compact list of exclusions. Every word adds value, with no redundancy or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless, read-only list operation with annotations and an output schema already present, the description provides all necessary context: what is returned, why, and what is intentionally omitted. Nothing important is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing for the description to explain beyond the schema. A baseline score of 4 is appropriate for a parameterless tool with full schema coverage.

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?

The description states a specific verb ('List') and resource ('users') and further clarifies that it returns minimal user identity for follow-up calls. The explicit list of excluded fields distinguishes it from a full user retrieval tool like get_user.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly signals when to use the tool: when minimal user identity is needed for follow-up calls. It does not explicitly name get_user as the alternative for fuller user details, but the context and exclusions make the usage boundary reasonably clear.

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