Skip to main content
Glama
Sign In
Nerdit

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_ai_budgets

Lists monthly AI gateway token limits and this UTC month's usage so you can spot apps nearing or over budget.

Instructions

List the monthly AI gateway token limits in force and this UTC month's use.

    Returns ``{default_tokens_month, budgets: [{service, tokens_month,
    used_tokens, month, state, own}]}``; ``state`` is ``ok``, ``warning``
    (80 %) or ``exceeded`` (the gateway answers that app 429
    ``budget_exceeded`` until the UTC month turns). ``own: false`` means
    the machine default alone applies. A non-admin sees its own apps only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_budgets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does it well: it discloses the return shape, the meaning of each state value, the concrete downstream consequence of 'exceeded' (gateway returns 429 budget_exceeded until the UTC month rolls over), the meaning of own:false, and the authorization-dependent visibility for non-admins. It stops short of stating there are no side effects or how large result sets behave, which keeps it below a 5.

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?

Front-loaded with purpose in the first sentence, followed by return shape and then state semantics in a logical order; every clause earns its place. Minor cost is the docstring-style backticks and formatting that read as copied internal documentation rather than description prose.

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?

For a zero-parameter, no-output-schema read tool, the description supplies everything an agent needs: what is returned, field-level semantics of state and own, the enforced consequence of exceeding budget, and the authorization-driven scope of results. Nothing material is left undocumented.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly adds no parameter prose.

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?

States a specific verb and resource ('List the monthly AI gateway token limits in force and this UTC month's use') and pins the exact object returned, so an agent can distinguish it from sibling writers like set_ai_budget and from usage-reporting tools like get_ai_usage without opening a schema.

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?

Usage is implied — you call this to inspect current budget state and this month's consumption — but there is no explicit when-to-use/when-not guidance and no named alternative for related questions (e.g. usage history vs. budget configuration). The 'non-admin sees its own apps only' clause hints at caller-dependent scope but does not route the agent anywhere.

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

Deploy Server

Other Tools