Skip to main content
Glama

list_trusted_advisor_checks

Retrieve available AWS Trusted Advisor checks to identify cost optimization, security, and performance improvement opportunities in your cloud environment.

Instructions

Lists Trusted Advisor checks available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that implements the list_trusted_advisor_checks tool by calling AWS Support API's DescribeTrustedAdvisorChecksCommand and formatting the response.
    if (name === "list_trusted_advisor_checks") {
        try {
            const command = new DescribeTrustedAdvisorChecksCommand({ language: "en" });
            const response = await supportClient.send(command);
            const checks = response.checks?.map(c => ({
                id: c.id,
                name: c.name,
                category: c.category
            })) || [];
            return { content: [{ type: "text", text: JSON.stringify(checks, null, 2) }] };
        } catch (error) {
            // Return clear error if Support API is not available (e.g. Basic Support plan)
            return { content: [{ type: "text", text: JSON.stringify({ error: "Trusted Advisor check failed. Ensure you have Business/Enterprise support or access.", details: (error as Error).message }) }] };
        }
    }
  • src/index.ts:777-781 (registration)
    Tool registration in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
        name: "list_trusted_advisor_checks",
        description: "Lists Trusted Advisor checks available.",
        inputSchema: { "type": "object", "properties": {} }
    }
  • Input schema definition for the tool (empty object, no parameters required).
    inputSchema: { "type": "object", "properties": {} }
  • Import of AWS SDK SupportClient and DescribeTrustedAdvisorChecksCommand used by the tool.
    import { SupportClient, DescribeTrustedAdvisorChecksCommand } from "@aws-sdk/client-support";
  • Initialization of the SupportClient instance used in the tool handler.
    const supportClient = new SupportClient({ region: "us-east-1" }); // AWS Support API is global (us-east-1)
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 offers minimal behavioral insight. It implies a read-only list operation but doesn't disclose details like pagination, rate limits, authentication needs, or what 'available' means (e.g., region-specific, account-level). This is inadequate for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it's front-loaded but could be more structured by including key details like scope or usage context to enhance clarity without sacrificing brevity.

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 tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is incomplete. It doesn't explain what Trusted Advisor checks are, the return format, or behavioral traits, leaving gaps that could hinder an agent's ability to use it effectively in context with many sibling tools.

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 no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 as it avoids redundancy while the schema fully covers the empty parameter set.

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

Purpose3/5

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

The description 'Lists Trusted Advisor checks available' clearly states the verb ('Lists') and resource ('Trusted Advisor checks'), but it's vague about scope and doesn't differentiate from siblings. It doesn't specify whether this lists all checks, only enabled ones, or checks for specific services, which could help distinguish it from other list_* tools.

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. The description doesn't mention prerequisites (e.g., AWS Trusted Advisor access), context for usage, or how it relates to other AWS monitoring tools in the sibling list, leaving the agent without usage direction.

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