Skip to main content
Glama

dynamodb_describe_ttl

Retrieve Time to Live (TTL) configuration for a DynamoDB table to manage data expiration and storage optimization.

Instructions

Get the TTL settings for a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYesName of the DynamoDB table

Implementation Reference

  • The core handler logic for the 'dynamodb_describe_ttl' tool. It retrieves the DynamoDB client and calls describe_time_to_live with the provided table_name argument.
    elif name == "dynamodb_describe_ttl":
        response = dynamodb_client.describe_time_to_live(
            TableName=arguments["table_name"]
        )
  • Defines the tool's metadata, description, and input schema for validation, specifying that 'table_name' is required.
    Tool(
        name="dynamodb_describe_ttl",
        description="Get the TTL settings for a table",
        inputSchema={
            "type": "object",
            "properties": {
                "table_name": {
                    "type": "string",
                    "description": "Name of the DynamoDB table"
                }
            },
            "required": ["table_name"]
        }
    ),
  • The MCP server handler that lists all available tools, including 'dynamodb_describe_ttl' via get_aws_tools().
    async def list_tools() -> list[Tool]:
        """List available AWS tools"""
        logger.debug("Handling list_tools request")
        return get_aws_tools()
  • Combines S3 and DynamoDB tools, including the 'dynamodb_describe_ttl' tool from get_dynamodb_tools().
    def get_aws_tools() -> list[Tool]:
        return [
            *get_s3_tools(),
            *get_dynamodb_tools()
        ]
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 tool retrieves TTL settings, implying a read-only operation, but doesn't specify required permissions, error conditions (e.g., if the table doesn't exist), rate limits, or the format of returned data. This leaves significant gaps for an agent to understand the tool's 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 directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by conveying essential information.

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 TTL settings are returned (e.g., status, attribute name), potential errors, or dependencies. For a tool that retrieves configuration data, more context about the output and operational constraints would help an agent use it effectively.

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 semantic context beyond what the schema provides, such as table naming conventions or validation rules. With high schema coverage, the baseline score of 3 is appropriate as 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 action ('Get') and resource ('TTL settings for a table'), making the purpose immediately understandable. It distinguishes itself from siblings like 'dynamodb_update_ttl' by focusing on retrieval rather than modification. However, it doesn't explicitly contrast with 'dynamodb_table_describe', which might provide broader table metadata.

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., table must exist), when not to use it, or how it differs from related tools like 'dynamodb_table_describe' that might also include TTL information. Usage is implied by the name 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