Skip to main content
Glama

dynamodb_table_describe

Retrieve detailed configuration and metadata for a specific DynamoDB table to understand its structure, settings, and current status.

Instructions

Get details about a DynamoDB table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYesName of the DynamoDB table

Implementation Reference

  • Executes the core logic of the dynamodb_table_describe tool by invoking the AWS DynamoDB describe_table API with the provided table name.
    elif name == "dynamodb_table_describe":
        response = dynamodb_client.describe_table(
            TableName=arguments["table_name"])
  • Defines the tool's name, description, and input schema requiring a 'table_name' parameter.
    Tool(
        name="dynamodb_table_describe",
        description="Get details about a DynamoDB table",
        inputSchema={
            "type": "object",
            "properties": {
                "table_name": {
                    "type": "string",
                    "description": "Name of the DynamoDB table"
                }
            },
            "required": ["table_name"]
        }
    ),
  • Registers all AWS tools, including dynamodb_table_describe, with the MCP server via the list_tools handler.
    async def list_tools() -> list[Tool]:
        """List available AWS tools"""
        logger.debug("Handling list_tools request")
        return get_aws_tools()
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Get details,' which implies a read-only operation, but doesn't clarify aspects like required permissions, rate limits, error handling, or what specific details are returned (e.g., table schema, status, metrics). For a tool with no annotations, 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, direct sentence with zero waste—'Get details about a DynamoDB table'—making it highly concise and front-loaded. Every word contributes to understanding the tool's purpose without unnecessary elaboration.

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 complexity of DynamoDB operations and the lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what details are returned (e.g., table attributes, throughput settings), potential errors, or dependencies. For a tool that retrieves metadata in a cloud service context, more context is needed to guide effective use.

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 single parameter 'table_name' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('Get details about') and resource ('a DynamoDB table'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'dynamodb_table_list' or 'dynamodb_describe_ttl', but the verb 'describe' is specific enough to imply retrieving metadata rather than listing or modifying.

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 siblings like 'dynamodb_table_list' (for listing tables) or 'dynamodb_describe_ttl' (for TTL-specific details), nor does it specify prerequisites such as needing an existing table. Usage is implied but not explicitly stated.

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/rishikavikondala/mcp-server-aws'

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