Skip to main content
Glama

Related Servers

Alternatives to ForgingStack Ration

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents and MCP-compatible clients to enforce multi-provider token-bucket and sliding-window rate limits, preventing TPM/RPM throttling across LLM APIs with predictive token consumption budgeting.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to track spending against configurable daily limits, record and undo expenses across daily, flexible, and safety pools, query remaining quota, manage budget rules, and receive quota alerts through a shared ledger. Supports read-only, bookkeeping, and budget-management permission levels.
      13
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and multi-agent frameworks to throttle outbound LLM API calls with multi-provider token-bucket and sliding-window limiting, plus predictive token-consumption budgeting to avoid TPM/RPM throttling. It runs deterministically over MCP with zero dependencies, returning rate-limit decisions and telemetry for any client such as Claude Desktop or Cursor.
      7
      -

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: pool lifecycle (create/get/list/topup/delete), unit consumption (draw), receipts (get_receipt), and billing (get_credits). The only near-pair, create_pool vs topup_pool, is cleanly separated by creation-vs-augmentation and by cost semantics. No two tools appear interchangeable.

    Naming Consistency4/5

    Seven of eight tools follow a consistent snake_case verb_noun pattern (create_pool, get_pool, list_pools, topup_pool, delete_pool, get_credits, get_receipt). The lone bare verb 'draw' breaks the pattern, though its meaning remains obvious.

    Tool Count5/5

    Eight tools is well within the sweet spot and every tool earns its place: CRUD on pools, the core draw operation, and supporting receipt/credit lookups. No redundancy or filler.

    Completeness4/5

    Pool lifecycle is well covered (create, read, list, topup, delete) plus draw and receipt retrieval, with billing visibility via get_credits. Gaps remain: no way to enumerate draws/receipts for a pool (receipts only fetchable by known id) and no way to adjust pool capacity or refill rate after creation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues