Skip to main content
Glama

list_users

Read-onlyIdempotent

Lists users with IDs, usernames, and companies, optionally filtering by name or username; use returned IDs to retrieve profiles, todos, or posts.

Instructions

List users with their user id, username and company.

    - name_contains: case-insensitive part of the full name or username; empty lists everyone.
    Use the user id with get_user, list_todos or search_posts. Contact details (email, phone,
    address) are never available through this server.
    

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

NameRequiredDescriptionDefault
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. Beyond that the description adds one genuinely useful behavioral fact: contact details (email, phone, address) are never exposed by this server, which prevents wasted calls. It does not discuss pagination or result limits, which is a notable omission for a list endpoint.

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

Conciseness4/5

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

Short and front-loaded: return shape first, then the single parameter, then downstream usage. The bullet indentation is slightly awkward, but every sentence carries information and nothing is padding.

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 one-parameter read-only list tool with no output schema, the description covers return fields, filter semantics, follow-up tools, and a data-availability constraint. Nothing an agent needs in order to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter, and it does: name_contains is case-insensitive, matches against full name or username, and an empty value returns everyone. That is more meaning than the bare string schema in the input definition provides.

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?

States a specific verb and resource ('List users') and immediately specifies the returned fields (user id, username, company). That field list also separates it from get_user, which the description later references, so an agent can tell the two apart without opening either schema.

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?

Gives concrete downstream guidance: use the returned user id with get_user, list_todos, or search_posts. It also clarifies the empty-filter case ('empty lists everyone'). What it lacks is an explicit when-not/alternative for enumerating users, but the follow-up routing is unusually actionable.

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

Deploy Server

Other Tools