Skip to main content
Glama
GT5041

return-billing-mcp-server

by GT5041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to return-billing-mcp-server

No user-submitted related servers found.

    Related Servers

    • ecommerce-mcp

      ritz541
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for commerce-operations self-service. Lets an AI agent look up order details and search orders without needing developer or SQL access.
      15 npm
      MIT

    • nhcx-payer-mcp

      umeshramya
      A
      license
      A
      quality
      B
      maintenance
      MCP server to simulate NHCX payer-side actions for testing provider integrations, enabling approval, rejection, querying, and forwarding of cases. It automates the payer workflow through tools like process case and get user role.
      5
      29 npm
      MIT

    • mcp-netsuite-practice

      awnt9
      F
      license
      A
      quality
      B
      maintenance
      MCP server that exposes read-only NetSuite tools for querying warehouse stock levels and order status, using mock data locally and a pluggable client interface.
      2
      -

    • test-data-mocking-mcp

      Charul0718
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that mocks payments, third-party API responses, and test data to enable QA flows for donation, checkout, SIP, and subscription pages without depending on a live gateway.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a generally distinct purpose, but lookup_order and get_billing_status both return order/billing information and could be confused. The descriptions clarify that lookup_order is for order details while get_billing_status focuses on billing status and payment instructions, but some overlap remains.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (lookup_order, check_return_eligibility, process_return, get_billing_status, escalate_to_human). The verbs vary but the pattern is uniform, making it easy to predict tool names.

    Tool Count5/5

    Five tools is well-scoped for a return/billing MCP server, covering the main customer service actions without unnecessary bloat. Each tool earns its place, and the count is within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core return and billing workflows: order lookup, eligibility check, return processing, billing status, and escalation. Minor gaps exist, such as no tool to view or update a return after processing, but the main user journey is complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources