Skip to main content
Glama
lishenxydlgzs

aws-athena-mcp

list_saved_queries

Retrieve all saved Athena queries from your AWS account to access and manage previously created SQL queries for data analysis.

Instructions

List all saved (named) Athena queries available in your AWS account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of list_saved_queries tool: lists Athena named queries using AWS SDK's ListNamedQueriesCommand and BatchGetNamedQueryCommand.
    async listNamedQueries(): Promise<{ namedQueries: { id: string; name: string; description?: string }[] }> {
      const listResponse = await this.client.send(
        new ListNamedQueriesCommand({
          ...(this.workGroup && { WorkGroup: this.workGroup })
        })
      );
    
      if (!listResponse.NamedQueryIds || listResponse.NamedQueryIds.length === 0) {
        return { namedQueries: [] };
      }
    
      const batchResponse = await this.client.send(
        new BatchGetNamedQueryCommand({ NamedQueryIds: listResponse.NamedQueryIds })
      );
    
      const namedQueries = (batchResponse.NamedQueries || []).map((query) => ({
        id: query.NamedQueryId || "",
        name: query.Name || "",
        description: query.Description,
      }));
    
      return { namedQueries };
    }
  • MCP CallToolRequest handler case for 'list_saved_queries' that invokes AthenaService.listNamedQueries() and returns JSON-formatted response.
    case "list_saved_queries": {
      const result = await this.athenaService.listNamedQueries();
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:136-143 (registration)
    Tool registration in ListToolsRequestHandler, including name, description, and empty input schema.
    {
      name: "list_saved_queries",
      description: "List all saved (named) Athena queries available in your AWS account.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what it does, not how it behaves. It doesn't disclose whether this requires specific IAM permissions, how results are paginated, if there are rate limits, or what the return format looks like.

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?

Single sentence with zero waste - every word contributes to understanding the tool's purpose. Front-loaded with the core action ('List all saved queries') followed by clarifying details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with no parameters and no output schema, the description is adequate but minimal. It doesn't address behavioral aspects like authentication requirements, result format, or limitations that would help an agent use it correctly.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('List all saved queries') and identifies the target resource ('named Athena queries in your AWS account'). It distinguishes from siblings like run_saved_query (executes) and get_result/status (retrieves query results/metadata).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving available saved queries, but doesn't explicitly state when to use this versus alternatives like run_saved_query or when not to use it. No prerequisites or exclusions are mentioned.

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/lishenxydlgzs/aws-athena-mcp'

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