Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

list_clients

Retrieve a list of all clients associated with a specific provider using the provider ID on the UseGrant MCP Server for efficient client management.

Instructions

List all clients

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerIdYesThe ID of the provider

Implementation Reference

  • The handler function for the list_clients tool. It takes a providerId, calls usegrant.listClients(providerId), and returns the clients as a JSON-formatted text content.
    async ({ providerId }) => {
      const clients = await usegrant.listClients(providerId);
      return {
        content: [{ type: 'text', text: JSON.stringify(clients, null, 2) }],
      };
    },
  • Input schema definition for the list_clients tool, specifying that providerId must conform to UgSchema.ProviderIdSchema.
    { providerId: UgSchema.ProviderIdSchema },
  • src/index.ts:69-79 (registration)
    Registration of the list_clients tool using McpServer.tool(), including the tool name, description, input schema, and handler function.
    server.tool(
      'list_clients',
      'List all clients',
      { providerId: UgSchema.ProviderIdSchema },
      async ({ providerId }) => {
        const clients = await usegrant.listClients(providerId);
        return {
          content: [{ type: 'text', text: JSON.stringify(clients, null, 2) }],
        };
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It doesn't disclose behavioral traits such as whether this is a read-only operation (implied by 'List'), pagination, rate limits, authentication needs, or error handling. The description is minimal and lacks context beyond the basic action.

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?

The description is extremely concise with a single phrase 'List all clients', which is front-loaded and wastes no words. Every part of the description earns its place by conveying the core action.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'clients' are, the return format, or any constraints (e.g., permissions needed). For a tool with one required parameter and no structured context, more detail is needed to be fully helpful.

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 the schema already documents the 'providerId' parameter. The description doesn't add any meaning beyond what the schema provides (e.g., why providerId is required, what happens if invalid). Baseline is 3 as the schema handles parameter documentation adequately.

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?

The description 'List all clients' clearly states the verb ('List') and resource ('clients'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_client' or 'list_tenants'. It doesn't specify what 'all' means in context (e.g., all clients for a provider, all clients globally).

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?

No guidance is provided on when to use this tool versus alternatives like 'get_client' (for a single client) or other list tools (e.g., 'list_providers'). The description implies a bulk retrieval, but there's no explicit comparison or exclusion criteria.

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

Related 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/usegranthq/mcp-server'

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