Skip to main content
Glama

get_instance_details

Retrieve detailed information about a specific EC2 instance to monitor its status, configuration, and resource usage within AWS environments.

Instructions

Retrieves detailed information about a specific EC2 instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesThe ID of the EC2 instance.

Implementation Reference

  • Handler that retrieves detailed EC2 instance information using DescribeInstancesCommand and returns it as JSON.
    if (name === "get_instance_details") {
        const instanceId = (args as any).instance_id;
        const command = new DescribeInstancesCommand({ InstanceIds: [instanceId] });
        const response = await ec2Client.send(command);
    
        const instance = response.Reservations?.[0]?.Instances?.[0];
    
        if (!instance) {
            return { content: [{ type: "text", text: "Instance not found." }] };
        }
    
        return { content: [{ type: "text", text: JSON.stringify(instance, null, 2) }] };
    }
  • src/index.ts:283-293 (registration)
    Tool registration in ListToolsRequestSchema handler, defining name, description, and input schema for get_instance_details.
    {
        name: "get_instance_details",
        description: "Retrieves detailed information about a specific EC2 instance.",
        inputSchema: {
            type: "object",
            properties: {
                instance_id: { type: "string", description: "The ID of the EC2 instance." }
            },
            required: ["instance_id"]
        }
    },
  • JSON schema for input validation: requires 'instance_id' string.
    inputSchema: {
        type: "object",
        properties: {
            instance_id: { type: "string", description: "The ID of the EC2 instance." }
        },
        required: ["instance_id"]
    }
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 'Retrieves' which implies a read-only operation, but doesn't clarify authentication requirements, rate limits, error conditions, or what 'detailed information' entails (e.g., state, type, tags). This is inadequate for a tool with zero annotation coverage.

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, well-structured sentence that gets straight to the point with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient for quick comprehension by an AI agent.

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 tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'detailed information' includes (e.g., JSON structure, fields), behavioral aspects like permissions or errors, or how it differs from sibling tools. This leaves significant gaps for an agent to understand the tool's full context.

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%, so the schema already documents the single 'instance_id' parameter. The description doesn't add any meaning beyond what's in the schema (e.g., format examples, validation rules, or where to find instance IDs). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Retrieves') and resource ('detailed information about a specific EC2 instance'), making the purpose immediately understandable. It distinguishes from sibling tools like 'list_ec2_instances' by focusing on a single instance rather than listing multiple. However, it doesn't specify what 'detailed information' includes, 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 prerequisites (e.g., needing an instance ID), contrast with 'list_ec2_instances' for bulk retrieval, or specify use cases like troubleshooting or monitoring. 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

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/bhaveshopss/MCP-server'

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