Skip to main content
Glama

List clients

list_clients
Read-onlyIdempotent

The clients: for an admin or the owner, every client (status active by default, archived or all); for another role, the clients of the projects that take its time, with ids and names.

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_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoFor an admin and the owner; another role reads the active records that take its time

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, non-open-world operation. The description adds meaningful behavioral context beyond that: visibility varies by role, and the default status filter is `active` unless `archived` or `all` is requested. It does not discuss ordering or pagination, but the output schema can carry return-shape details.

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

Conciseness3/5

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

The description is a single sentence with no filler, but the nested parentheticals and backtick formatting make it dense and somewhat awkward to parse. The lead-in 'The clients:' is terse and less directly informative than an explicit verb phrase.

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

Completeness4/5

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

Given one optional parameter, full schema coverage, a present output schema, and rich annotations, the description supplies the key missing context: role-based visibility and default filtering. Only pagination and ordering details are absent, and those are plausibly covered by the output schema.

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

Parameters3/5

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

Schema description coverage is 100% and the `status` enum is fully documented, so a baseline of 3 is appropriate. The description restates the enum options and adds the `active` default plus role restrictions, but adds limited meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource (listing clients) and adds role-dependent scope: admins/owners see every client filtered by status, while other roles see only clients of projects that take their time, with ids and names. It does not explicitly contrast with the get_client sibling for single-record retrieval, keeping it just short of a 5.

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

Usage Guidelines3/5

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

Usage is implied through the role-based behavior and the default `active` filter, giving an agent a reasonable sense of when the tool applies. However, there is no explicit when-to-use/when-not guidance or pointer to alternatives like get_client for a single client.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources