Skip to main content
Glama
jjikky

DynamoDB Read-Only MCP

by jjikky

list-tables

Retrieve a comprehensive list of all DynamoDB tables directly from the DynamoDB Read-Only MCP server to manage and analyze your database structure efficiently.

Instructions

Get a list of all DynamoDB tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:22-45 (registration)
    Registration of the 'list-tables' tool, including inline handler that invokes listTables helper, formats the response as text content, and handles errors.
    server.tool('list-tables', 'Get a list of all DynamoDB tables', {}, async () => {
      try {
        console.error('# list-tables tool has been called');
        const tables = await listTables();
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(tables, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          isError: true,
          content: [
            {
              type: 'text',
              text: `Error occurred: ${error.message}`,
            },
          ],
        };
      }
    });
  • Core handler logic for listing DynamoDB tables using ListTablesCommand on the DynamoDB client.
    export async function listTables() {
      console.error('# Starting listTables function');
      try {
        const command = new ListTablesCommand({});
        console.error('# ListTables command created successfully');
        const response = await dynamodb.send(command);
        console.error('# ListTables response received:', response);
        return response.TableNames || [];
      } catch (error) {
        console.error('# Error in listTables function:', error);
        throw error;
      }
    }
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 what the tool does but doesn't cover critical aspects like whether it's read-only, requires authentication, has rate limits, or what the output format looks like (e.g., pagination, error handling). This leaves significant gaps for an agent.

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, clear sentence with no wasted words, making it front-loaded and easy to parse. It efficiently conveys the core action without unnecessary elaboration, earning full marks for conciseness.

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 incomplete. It doesn't explain behavioral traits, return values, or usage context, which are essential for an agent to operate this tool effectively in a real-world scenario.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without redundancy.

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 resource ('list of all DynamoDB tables'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'describe-table' or 'scan-table' that also involve table operations, missing explicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this is for metadata listing versus data retrieval (like 'scan-table') or if there are prerequisites such as permissions. The description lacks context for selection among siblings.

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/jjikky/dynamo-readonly-mcp'

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