Skip to main content
Glama

list_clients

Search the workspace's clients by name or email. Returns id, name, email, billing address. Use this to find a clientId before creating an invoice.

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
pageNo
searchNoCase-insensitive match on name or email
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the returned fields and that the operation is a search over name/email. However it says nothing about pagination behavior (page/pageSize exist), default page size, sort order, or result caps, leaving meaningful behavioral gaps for a caller.

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?

Two sentences with no waste: purpose and payload first, then the routing rationale. Front-loaded and easy to scan.

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?

For a simple zero-required-parameter read tool with no output schema, stating the returned fields and the retrieval use case is close to sufficient. The remaining gap is pagination semantics, which neither structured fields nor the description explain.

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

Parameters2/5

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

Schema coverage is only 33% – only 'search' is documented, and the description merely restates that matching happens on name or email. The 'page' and 'pageSize' parameters get no explanation in either the schema or the description, so the description fails to compensate for the low coverage.

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 specific verb and resource ('Search the workspace's clients') plus the matching fields and the return payload, which lets an agent separate it from invoice/document tools. It stops short of explicitly distinguishing itself from sibling 'create_client', but the read-only search framing makes the difference obvious.

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 an explicit use case: find a clientId before creating an invoice, which ties it to 'create_invoice' workflow. No when-not guidance or alternatives (e.g., when to use a get-client tool instead), but the positive guidance is concrete and actionable.

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