Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

get_client

Retrieve client details by specifying provider and client IDs using the UseGrant MCP Server. Simplify client management and access information with this tool.

Instructions

Get client details by provider and client ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYesThe ID of the client
providerIdYesThe ID of the provider

Implementation Reference

  • The handler function for the 'get_client' tool. It takes providerId and clientId, calls usegrant.getClient from the SDK, and returns the client details as a JSON-formatted text content response.
    async ({ providerId, clientId }) => {
      const client = await usegrant.getClient(providerId, clientId);
      return {
        content: [{ type: 'text', text: JSON.stringify(client, null, 2) }],
      };
    },
  • Input schema definition for the 'get_client' tool, specifying providerId and clientId using Zod schemas from the UseGrant SDK.
    {
      providerId: UgSchema.ProviderIdSchema,
      clientId: UgSchema.ClientIdSchema,
    },
  • src/index.ts:93-106 (registration)
    Registration of the 'get_client' tool on the MCP server using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      'get_client',
      'Get client details by provider and client ID',
      {
        providerId: UgSchema.ProviderIdSchema,
        clientId: UgSchema.ClientIdSchema,
      },
      async ({ providerId, clientId }) => {
        const client = await usegrant.getClient(providerId, clientId);
        return {
          content: [{ type: 'text', text: JSON.stringify(client, null, 2) }],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose if it's read-only, requires authentication, handles errors, returns structured data, or has rate limits, which are critical for a retrieval tool.

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 a single, efficient sentence that front-loads the core purpose without any fluff or redundancy. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 the tool's complexity (retrieval with two required parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'client details' includes, error handling, or return format, leaving significant gaps for the agent to infer behavior.

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?

The description adds minimal semantics by naming the parameters ('provider and client ID'), but the input schema already has 100% coverage with clear descriptions for both parameters. This meets the baseline of 3, as the schema does the heavy lifting without needing extra detail.

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?

The description clearly states the action ('Get') and resource ('client details') with specific identifiers ('by provider and client ID'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_clients' or 'get_provider', which would require 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'list_clients' for browsing or 'get_provider' for provider details. It lacks context about prerequisites, error conditions, or typical use cases, leaving the agent without usage direction.

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