Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FORGINGSTACK_API_KEYYesYour ForgingStack Ration API key, obtained from signup (returned once). Required to authenticate calls that create pools or draw units.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_poolC

Create a token-bucket quota pool shared by many agents. Costs 1 credit. Returns the pool with its starting availability.

drawA

Draw units from a pool for one agent. Returns allowed or denied, a reason, and a hash-chained receipt. Costs 1 credit per draw call, allowed or denied; an idempotency key replay is free.

get_poolB

Fetch one pool by id, with its current available units (refill applied).

list_poolsA

List all pools owned by the configured API key.

topup_poolC

Add units to a pool, clamped at capacity. Free — no billing credit is charged.

delete_poolA

Delete a pool and its draws. No billing credit is charged or refunded.

get_creditsB

Remaining credit balance for the configured API key.

get_receiptC

Fetch a past draw receipt by id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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