Skip to main content
Glama

list_dynamodb_tables

Retrieve a list of DynamoDB tables from AWS to manage and monitor your database resources.

Instructions

Lists DynamoDB tables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that lists DynamoDB tables using ListTablesCommand and returns the table names.
    if (name === "list_dynamodb_tables") {
        const command = new ListTablesCommand({});
        const response = await dynamoDbClient.send(command);
        return { content: [{ type: "text", text: JSON.stringify(response.TableNames || [], null, 2) }] };
    }
  • src/index.ts:772-776 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
        name: "list_dynamodb_tables",
        description: "Lists DynamoDB tables.",
        inputSchema: { "type": "object", "properties": {} }
    },
  • Input schema definition: empty object (no parameters).
    inputSchema: { "type": "object", "properties": {} }
  • DynamoDB client initialization used by the handler.
    const dynamoDbClient = new DynamoDBClient({});
  • Import for DynamoDB client and ListTablesCommand.
    import { DynamoDBClient, ListTablesCommand, DescribeTableCommand } from "@aws-sdk/client-dynamodb";
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Lists DynamoDB tables' implies a read-only operation but doesn't specify whether this requires specific IAM permissions, returns all tables or just those accessible to the caller, includes pagination details, or provides any metadata about the tables. For a cloud resource listing tool with zero annotation coverage, this is insufficient.

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 no wasted words. It's front-loaded with the essential information and perfectly sized for its purpose.

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 cloud resource listing tool with no annotations and no output schema, the description is inadequate. It doesn't explain what information is returned (just table names? ARNs? status?), whether results are paginated, what permissions are required, or any AWS region/account context. The description should provide more operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters (schema coverage 100%), so no parameter documentation is needed. The description doesn't attempt to explain nonexistent parameters, which is appropriate. A baseline of 4 is correct for zero-parameter tools.

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 ('Lists') and resource ('DynamoDB tables'), making the purpose immediately understandable. It doesn't differentiate from sibling tools, but since all siblings are distinct AWS resource listing operations (like list_s3_buckets, list_ec2_instances), the lack of differentiation is less critical here.

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. While the sibling tools are all distinct AWS resource types, there's no explicit mention of when this specific listing operation is appropriate versus other AWS inventory tools.

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