Skip to main content
Glama
Scoped Support Tools Server

Scoped Support Tools Server

by AIwithhassan

Related Servers

Alternatives to Scoped Support Tools Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure support-ticket and customer-account operations with signed JWT authentication, prompt-injection and tool-poisoning guardrails, and human-in-the-loop confirmation for destructive actions.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and signed-in support staff to search and read customer tickets, add internal notes, issue refunds under per-scope and per-customer limits, and export ticket data over a remote, OAuth-protected Streamable HTTP endpoint. Tool lists, resources, prompts, and write operations are gated by bearer tokens and audience-bound scopes so that refund and export actions stay bounded.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access corporate HR and CRM APIs on behalf of a specific user through OAuth 2.1 token verification, deny-by-default RBAC, token exchange, audit logging, PII masking, and untrusted-output envelopes.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely perform privileged actions like creating GitHub issues by minting short-lived, single-purpose tokens on demand, with policy enforcement and audit logging.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely invoke tools by enforcing identity proof, capability verification, and risk scoring on every request, blocking unsafe calls before they execute.
      MIT

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action: customer lookup, listing, order ID retrieval, refund processing, product info, and a generic answer fallback. The only potential overlap is answer_user_query, but its purpose as a canned-response fallback is clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., process_refund, get_order_id, list_customers). No mixed conventions or unclear verbs.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a support-focused toolkit. The number is reasonable and each tool has a clear role without unnecessary redundancy.

    Completeness4/5

    Core support workflows are covered: customer lookup, product info, order ID retrieval, refund processing, and generic canned answers. Minor gaps exist (e.g., no order detail retrieval beyond ID), but these can be worked around with the existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues