bifrost-budget
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIFROST_HOST | No | Host to bind the HTTP server to. | 0.0.0.0 |
| BIFROST_PORT | No | Port to bind the HTTP server to. | 8080 |
| BIFROST_MCP_PATH | No | Path for the MCP endpoint. | /mcp |
| BIFROST_LOG_LEVEL | No | Controls the structured application logs. | INFO |
| BIFROST_TRANSPORT | No | Transport mode: streamable-http (default) or stdio. | streamable-http |
| BIFROST_QUOTA_PATH | No | Path to the quota endpoint. | /api/governance/virtual-keys/quota |
| BIFROST_VIRTUAL_KEY | No | Fallback caller key for local development or explicit non-production use only. | |
| BIFROST_API_BASE_URL | Yes | Base URL for the Bifrost API, for example https://bifrost.example.com | |
| BIFROST_TIMEOUT_SECONDS | No | Timeout for upstream requests in seconds. | 15 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_quotaA | Return the caller's Bifrost quota snapshot by calling the configured quota endpoint with the caller's Authorization header when present. Explicit virtual_key, x-bf-vk, and BIFROST_VIRTUAL_KEY remain available for local and non-production fallback use. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its description clearly scopes it to retrieving a Bifrost quota snapshot.
The single tool name 'get_quota' follows a clear verb_noun convention and is descriptive. There are no other names to create inconsistency.
One tool is minimal and feels thin for a server named 'bifrost-budget'. It may be acceptable as a narrow quota-check adapter, but the count is borderline.
The tool surface only supports reading a quota snapshot, with no create, update, delete, or list operations. This leaves significant gaps if the server is meant to support budget or quota management workflows.