Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-essential-subscription-by-id

Retrieve details of a specific Redis Cloud essential subscription using its unique ID to manage your account resources effectively.

Instructions

Get an essential subscription by ID for the current Cloud Redis account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriptionIdYesSubscription ID

Implementation Reference

  • Handler function that extracts subscriptionId, validates input using subscriptionIdSchema, calls SubscriptionsEssentialsService.getSubscriptionById1, and returns the result wrapped in createToolResponse.
    "get-essential-subscription-by-id": async (request) => {
      const { subscriptionId } = extractArguments<{ subscriptionId: number }>(
        request,
      );
    
      // Validate input
      validateToolInput(
        subscriptionIdSchema,
        { subscriptionId },
        "Essential subscription ID",
      );
    
      const subscription = await executeApiCall(
        () => SubscriptionsEssentialsService.getSubscriptionById1(subscriptionId),
        `Get essential subscription ${subscriptionId}`,
      );
      return createToolResponse(subscription);
    },
  • Tool definition object including name, description, and inputSchema specifying subscriptionId as required number >=1.
    const GET_ESSENTIAL_SUBSCRIPTION_BY_ID_TOOL: Tool = {
      name: "get-essential-subscription-by-id",
      description:
        "Get an essential subscription by ID for the current Cloud Redis account",
      inputSchema: {
        type: "object",
        properties: {
          subscriptionId: {
            type: "number",
            description: "Subscription ID",
            min: 1,
          },
        },
        required: ["subscriptionId"],
      },
    };
  • Export of the array of Tool objects, registering 'get-essential-subscription-by-id' tool among essential subscriptions tools.
    export const SUBSCRIPTIONS_ESSENTIALS_TOOLS = [
      GET_ESSENTIAL_SUBSCRIPTIONS_TOOL,
      GET_ESSENTIAL_SUBSCRIPTION_BY_ID_TOOL,
      CREATE_ESSENTIAL_SUBSCRIPTION_TOOL,
      DELETE_ESSENTIAL_SUBSCRIPTION_TOOL,
      GET_ESSENTIALS_PLANS_TOOL,
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify authentication needs, error conditions, rate limits, or what happens if the subscription ID doesn't exist. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a simple retrieval tool with one parameter and no output schema, the description covers the basic purpose adequately. However, without annotations and with sibling tools that perform similar operations, it lacks sufficient context about when to choose this tool and what behavioral characteristics to expect.

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, with the subscriptionId parameter clearly documented. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 the resource 'essential subscription by ID', specifying it's for the current Cloud Redis account. It distinguishes from sibling tools like get-essential-subscriptions (plural) by focusing on a single ID, but doesn't explicitly contrast with get-pro-subscription or other similar tools.

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 like get-essential-subscriptions (for listing) or get-pro-subscription (for pro tier). It mentions 'for the current Cloud Redis account' which gives some context but doesn't specify prerequisites, exclusions, or comparative 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/redis/mcp-redis-cloud'

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