Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

get_provider

Retrieve provider details by ID from the UseGrant MCP Server to efficiently manage and access provider information in the platform.

Instructions

Get a provider by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the provider

Implementation Reference

  • Handler function for the 'get_provider' tool. It takes an 'id' parameter, fetches the provider using usegrant.getProvider(id), and returns the provider data as JSON-formatted text content.
    async ({ id }) => {
      const provider = await usegrant.getProvider(id);
      return {
        content: [{ type: 'text', text: JSON.stringify(provider, null, 2) }],
      };
    },
  • Input schema for the 'get_provider' tool, requiring an 'id' field validated by UgSchema.ProviderIdSchema.
    { id: UgSchema.ProviderIdSchema },
  • src/index.ts:45-55 (registration)
    Registration of the 'get_provider' MCP tool using server.tool(), including name, description, schema, and handler function.
    server.tool(
      'get_provider',
      'Get a provider by ID',
      { id: UgSchema.ProviderIdSchema },
      async ({ id }) => {
        const provider = await usegrant.getProvider(id);
        return {
          content: [{ type: 'text', text: JSON.stringify(provider, 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 states the action ('Get') but doesn't disclose behavioral traits: whether it's a read-only operation, requires authentication, has rate limits, returns error if ID is invalid, or what the output format might be. For a retrieval tool with zero annotation coverage, this is a significant gap.

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 ('Get a provider by ID')—a single, clear sentence with zero waste. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't cover behavioral aspects (e.g., read-only nature, error handling) or output expectations, leaving gaps for an AI agent to infer. For a basic retrieval tool, more context would be helpful despite the straightforward schema.

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 meaning beyond the input schema. It mentions 'by ID', which aligns with the schema's single 'id' parameter (100% coverage). No additional details on ID format, validation, or examples are provided. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 'Get a provider by ID' clearly states the verb ('Get') and resource ('provider'), and specifies the lookup mechanism ('by ID'). It distinguishes from siblings like 'list_providers' (which retrieves multiple providers) and 'get_tenant_provider' (which involves tenant context). However, it doesn't explicitly contrast with these alternatives in the description text itself.

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. It doesn't mention prerequisites (e.g., needing a valid provider ID), contrast with 'list_providers' for bulk retrieval, or specify scenarios where this is appropriate (e.g., detailed view of a single known provider). Usage is implied but not articulated.

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