Skip to main content
Glama

List customers

list_customers
Read-onlyIdempotent

List your customers.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25, max 100)
cursorNonext_cursor from the previous page
external_idNoFind the customer with this external_id (0 or 1 results)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page"
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 25, max 100)"
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description contributes no behavioral context of its own — no note on pagination behavior, ordering, result volume, or what happens when external_id matches nothing.

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?

A single short sentence is front-loaded and contains zero waste, but it also contains almost no information — the brevity reflects under-specification rather than disciplined editing. It is not verbose, just nearly empty.

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

Completeness3/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 full schema coverage and an unambiguous name, this is minimally sufficient to invoke. It stops short of explaining pagination practice or that external_id narrows the call to a single result, which would help an agent choose correctly.

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%, so limit, cursor and external_id are each documented in the schema itself, including the default/max and the 0-or-1 match semantics. The description adds no meaning beyond that, so the baseline 3 applies.

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

Purpose3/5

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

"List your customers" gives a clear verb and resource, so an agent knows the general operation. However, it adds nothing beyond the tool name and title, and it does not distinguish this from nearby siblings such as get_customer (single-record fetch) or list_contacts (different resource with similar listing semantics).

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer get_customer over list_customers, and no indication of how the external_id filter interacts with a full listing. The agent must infer the routing decision entirely from the tool name.

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.