Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

list_providers

Retrieve a comprehensive list of all providers managed through the UseGrant MCP Server, enabling efficient provider management and access control.

Instructions

List all providers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_providers' MCP tool. It calls usegrant.listProviders() to fetch providers and returns them formatted as JSON in the MCP response format. This also serves as the registration since the handler is defined inline.
    server.tool('list_providers', 'List all providers', async () => {
      const providers = await usegrant.listProviders();
      return {
        content: [{ type: 'text', text: JSON.stringify(providers, 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 for behavioral disclosure. 'List all providers' implies a read-only operation but doesn't specify whether it's paginated, sorted, or includes metadata. It lacks details on rate limits, authentication needs, or what 'all' entails (e.g., active only, includes deleted). For a tool with zero annotation coverage, this is insufficient.

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 ('List all providers')—just three words that directly convey the core action. It's front-loaded with no wasted words, making it easy to parse quickly. This is an example of efficient communication.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate. However, without annotations or output schema, it doesn't explain what the list returns (e.g., provider objects, IDs only) or behavioral aspects. For a basic list operation among many siblings, it could benefit from slightly more context about scope or format.

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?

The tool has 0 parameters, and schema description coverage is 100% (though schema is empty). The description doesn't need to explain parameters, so it meets baseline expectations. No additional parameter information is required or provided.

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 'List all providers' clearly states the verb ('List') and resource ('providers'), making the purpose immediately understandable. It distinguishes from siblings like 'get_provider' (singular retrieval) and 'create_provider' (creation). However, it doesn't specify scope (e.g., all providers in the system vs. filtered), which prevents a perfect score.

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 when to choose 'list_providers' over 'get_provider' for single retrieval, or how it relates to other list tools like 'list_tenants' or 'list_clients'. There's no context about prerequisites, permissions, or typical use cases.

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