Skip to main content
Glama
lindoai

mcp-lindoai

Official

list_clients

Read-only

Retrieve a list of all clients in your Lindo AI workspace.

Instructions

List all clients in the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `list_clients` tool handler. Registered via `server.tool()` with name 'list_clients'. It takes no parameters, calls apiCall('GET', '/v1/workspace/client/list') and returns the JSON response.
    server.tool(
      "list_clients",
      "List all clients in the workspace.",
      {},
      { title: "List Clients", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async () => {
        const data = await apiCall("/v1/workspace/client/list", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Registration of the 'list_clients' tool using `server.tool()`. The MCP server registers the tool name, description, empty schema, metadata (title 'List Clients', readOnlyHint: true), and the async handler function.
    server.tool(
      "list_clients",
      "List all clients in the workspace.",
      {},
      { title: "List Clients", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async () => {
        const data = await apiCall("/v1/workspace/client/list", "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The input schema for list_clients is an empty object `{}`, meaning it accepts no parameters.
    "list_clients",
Behavior2/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds no further behavioral context (e.g., pagination, ordering). It barely goes beyond what annotations provide.

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?

Single sentence, front-loaded, no wasted words. Appropriate for a simple list operation.

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 no parameters and no output schema, the description is mostly complete. It could mention that it returns a list of client objects, but the lack of such detail is acceptable for a trivial tool.

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?

Input schema has no parameters (100% coverage, 0 params). Baseline is 4. Description adds no parameter info, but none is needed.

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 clearly states the action 'list' and the resource 'clients', with scope 'all in workspace'. It distinguishes from sibling tools like create_client, update_client, and other list tools.

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?

No explicit guidance on when to use or avoid this tool. However, given its simplicity and the existence of distinct sibling tools, usage is implied but not elaborated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lindoai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server