Skip to main content
Glama
usegranthq

UseGrant MCP Server

Official
by usegranthq

get_tenant

Retrieve tenant details by ID using the UseGrant MCP Server to manage and access tenant-specific information within the platform.

Instructions

Get a tenant by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the tenant

Implementation Reference

  • Handler function that retrieves a tenant by ID using the UseGrant SDK and returns it as a JSON string in the MCP response format.
    async ({ id }) => {
      const tenant = await usegrant.getTenant(id);
      return {
        content: [{ type: 'text', text: JSON.stringify(tenant, null, 2) }],
      };
    },
  • Input schema for the get_tenant tool, specifying the required 'id' parameter validated by UgSchema.TenantIdSchema.
    {
      id: UgSchema.TenantIdSchema,
    },
  • src/index.ts:232-244 (registration)
    Registration of the 'get_tenant' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool(
      'get_tenant',
      'Get a tenant by ID',
      {
        id: UgSchema.TenantIdSchema,
      },
      async ({ id }) => {
        const tenant = await usegrant.getTenant(id);
        return {
          content: [{ type: 'text', text: JSON.stringify(tenant, 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 the full burden. It states 'Get' implies a read operation but lacks details on permissions, rate limits, error handling (e.g., invalid ID), or return format. For a tool with zero annotation coverage, this is insufficient behavioral disclosure.

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 with zero wasted words. It's front-loaded with the core action ('Get a tenant'), making it easy to parse quickly. Every word earns its place.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'tenant' is in this context, what data is returned, or how errors are handled. For a read operation with no structured output documentation, more context is needed.

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%, with the parameter 'id' documented as 'The ID of the tenant'. The description adds no additional meaning beyond this, such as ID format or sourcing. With high schema coverage, the baseline score of 3 is appropriate.

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 verb ('Get') and resource ('a tenant by ID'), making the purpose unambiguous. However, it doesn't distinguish this tool from other 'get_' siblings like get_client or get_provider, which follow the same pattern but target different resources.

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 tenant ID), contrast with list_tenants for browsing, or specify error conditions. Without such context, an agent might misuse it.

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