Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

list_tenants

Retrieve a complete list of tenants managed on the UseGrant MCP Server to streamline provider, client, and access token administration.

Instructions

List all tenants

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'list_tenants' MCP tool. It calls usegrant.listTenants() from the UseGrant SDK to fetch all tenants and returns the result as a JSON-formatted text content block. This is also the registration site since the handler is inline.
    server.tool('list_tenants', 'List all tenants', async () => {
      const tenants = await usegrant.listTenants();
      return {
        content: [{ type: 'text', text: JSON.stringify(tenants, 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 offers minimal behavioral insight. 'List all tenants' implies a read-only operation but doesn't disclose pagination, sorting, filtering, rate limits, authentication requirements, or return format. For a list operation with zero annotation coverage, this is inadequate.

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 maximally concise - three words that directly convey the core functionality without any fluff. It's front-loaded and every word earns its place, making it efficient for agent comprehension.

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?

For a list operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'tenants' are in this context, what data is returned, whether results are paginated, or any system constraints. The agent lacks necessary context to use this tool effectively.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose. Baseline 4 is correct for zero-parameter tools.

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 tenants' clearly states the verb ('List') and resource ('tenants'), making the purpose immediately understandable. It distinguishes from siblings like 'get_tenant' (singular retrieval) and 'create_tenant' (creation). However, it lacks specificity about scope or format, preventing 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 prerequisites, compare with 'get_tenant' for single-tenant retrieval, or explain when listing is appropriate versus other list_* tools. This leaves the agent without contextual usage cues.

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