Skip to main content
Glama

select-tenant

Switch between Azure tenants and subscriptions to manage resources across different organizational accounts. Specify tenant and subscription IDs to change your working context.

Instructions

Select Azure tenant and subscription

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenantIdYesAzure Tenant ID to select
subscriptionIdYesAzure Subscription ID to select

Implementation Reference

  • The handler function that executes the select-tenant tool. Parses arguments using SelectTenantSchema, initializes Azure clients for the given tenant and subscription, and returns a success message.
    private async handleSelectTenant(args: any) {
      const { tenantId, subscriptionId } = SelectTenantSchema.parse(args);
      await this.initializeClients(tenantId, subscriptionId);
      return this.createTextResponse(
        "Tenant and subscription selected! Clients initialized."
      );
    }
  • Tool registration in handleListTools method, defining name, description, and input schema for select-tenant.
    {
      name: "select-tenant",
      description: "Select Azure tenant and subscription",
      inputSchema: {
        type: "object",
        properties: {
          tenantId: {
            type: "string",
            description: "Azure Tenant ID to select",
          },
          subscriptionId: {
            type: "string",
            description: "Azure Subscription ID to select",
          },
        },
        required: ["tenantId", "subscriptionId"],
      },
    },
  • Standalone Zod schema for validating select-tenant tool inputs, used in the handler.
    const SelectTenantSchema = z.object({
      tenantId: z.string().describe("Azure Tenant ID to select"),
      subscriptionId: z.string().describe("Azure Subscription ID to select"),
    });
  • Switch case in handleCallTool that routes select-tenant calls to the handler function.
    case "select-tenant":
      result = await this.handleSelectTenant(args);
      break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Select') but doesn't explain what this means operationally—e.g., whether it sets a context for subsequent calls, requires specific permissions, has side effects like caching, or returns any confirmation. This is inadequate for a tool that likely influences session state.

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 and resources, making it immediately understandable. This is an excellent example of conciseness.

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 for a tool that likely manages session context. It doesn't explain the behavioral impact of 'selecting' (e.g., persistence, scope for other tools), return values, or error conditions. For a state-changing operation in a cloud environment, this leaves critical gaps.

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 input schema has 100% description coverage, clearly documenting both parameters (tenantId and subscriptionId) with their purposes. The description adds no additional parameter details beyond what the schema provides, so it meets the baseline score of 3 without compensating value.

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 ('Select') and the target resources ('Azure tenant and subscription'), which is specific and unambiguous. However, it doesn't differentiate this tool from sibling tools like 'list-tenants' or explain how selection differs from listing, 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 (e.g., authentication state), whether it's needed before other operations, or how it relates to siblings like 'list-tenants' for discovery. This leaves the agent with minimal context for appropriate invocation.

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

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/kalivaraprasad-gonapa/azure-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server