Skip to main content
Glama
KuudoAI

amazon-agent-atlas-mcp

by KuudoAI

Related Servers

Alternatives to amazon-agent-atlas-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
      Not graded
      quality
      C
      maintenance
      Exposes Amazon Selling Partner API tools for sellers to manage orders, inventory, listings, pricing, analytics, and reports via natural language.
      4 npm
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables external agents to retrieve knowledge with source context through MCP tools for querying, listing collections, and obtaining document summaries.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.
      -

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: tags and search both help discover tools, but by different routes (tag browsing vs. query search). get_schema and execute are clearly separate for detail retrieval and execution. Minor overlap exists between tags and search, but descriptions sufficiently clarify the difference.

    Naming Consistency3/5

    Names are simple and lowercase, but not fully consistent: 'tags' is a noun while 'search', 'get_schema', and 'execute' are verbs (or verb_noun in the case of get_schema). There is no chaotic mixing of conventions, but the pattern is not uniform.

    Tool Count5/5

    With 4 tools, the set is well-scoped for its purpose: discover by tag, search, get schema, and execute. Every tool serves a distinct role in the workflow and none is superfluous.

    Completeness4/5

    The set covers the core lifecycle of browsing, searching, schematizing, and executing remote tools. A minor gap is the lack of a direct 'list all tools' operation; discovery relies on tags or search, but the workflow is otherwise complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues