Skip to main content
Glama
ypollak2

ypollak2/llm-router

by ypollak2
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

llm_budget

Shows real-time budget pressure for all configured providers, normalizing quota into a single pressure value from 0.0 to 1.0.

Instructions

Show real-time budget pressure for all configured providers (v5.0+).

Reads live budget state from the Budget Oracle, which normalises provider
quota into a single pressure value (0.0 = fully available, 1.0 = exhausted).

Pressure sources by provider type:
  Local (Ollama, vLLM)  — always 0.0 (free, no quota)
  Claude subscription   — max(session_pct, weekly_pct, sonnet_pct) / 100
  API-key providers     — monthly spend / configured cap (0.0 if no cap)

Returns:
    A formatted budget summary with pressure bars per provider.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but description is thorough: explains it reads live budget state from Budget Oracle, normalizes to pressure value, and details sources per provider type. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with a clear intro, provider-specific details, and return value. Slightly verbose but every sentence adds value; front-loads the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no parameters and an output schema; description covers the return format. Given the simplicity, the description is complete and sufficient for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters, so schema coverage is 100%. Description adds meaning by explaining output format and pressure calculation, exceeding baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Show real-time budget pressure for all configured providers' and explains the normalized pressure value. It differentiates from siblings like llm_check_usage and llm_quota_status by focusing on the consolidated budget pressure across providers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs. alternatives like llm_check_usage or llm_quota_status. The description implies its use for budget pressure overview but lacks when-not or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ypollak2/llm-router'

If you have feedback or need assistance with the MCP directory API, please join our Discord server