Skip to main content
Glama
eisuke000111

AWS Customer Playbook Advisor MCP

by eisuke000111

Related Servers

Alternatives to AWS Customer Playbook Advisor MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables users to access, search, and get recommendations from AWS documentation through natural language queries. Supports both global AWS documentation and AWS China documentation with tools to fetch pages, search content, and discover related resources.
      3
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Provides instant access to authoritative security documentation from organizations like OWASP, NIST, and major cloud providers through natural language semantic search. It enables users to retrieve security best practices, frameworks, and vulnerability information directly from a locally cached knowledge base.
      4
      1
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides structured access to OCSF-normalized security data stored in Amazon Security Lake, enabling AI assistants to search for IP addresses, GuardDuty findings, and explore available data sources.
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables cloud and platform engineers to investigate AWS incidents by grounding responses in approved runbooks and operational evidence, with authenticated access, citations, observability, and human approval before any write action.
      MIT

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation3/5

    The tools have some overlap in purpose, as all three retrieve AWS security playbooks or guidance, making them potentially confusing. However, descriptions help differentiate them: get_aws_playbook fetches a specific playbook, get_prevention_guidance focuses on preventive guidance, and list_available_playbooks lists available options. This reduces ambiguity but doesn't eliminate it entirely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: get_aws_playbook, get_prevention_guidance, and list_available_playbooks. The verbs 'get' and 'list' are clear and predictable, with no deviations in style or convention across the set.

    Tool Count3/5

    With only 3 tools, the count feels thin for a server focused on AWS security playbooks, as it may lack operations like creating, updating, or deleting playbooks. However, it's reasonable for a read-only advisory service, though it borders on being under-scoped for typical agent workflows.

    Completeness2/5

    The tool surface is significantly incomplete for the domain of AWS security playbook management. It only supports retrieval and listing operations, with no tools for creating, updating, or applying playbooks. This will likely cause agent failures when trying to perform full lifecycle management, leaving obvious gaps in coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues