Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

list_budgets

Read-only

Retrieve cloud spending budgets with names, amounts, and utilization. Filter budgets by owner, creation time, or name to check budget status.

Instructions

Use this when the user wants to see their cloud spending budgets or check budget status. Returns a paginated list of budgets with names, amounts, and utilization. Do NOT use this for cost analysis (use run_query) or spending alerts (use list_alerts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoThe maximum number of results to return in a single page. Defaults to 50.
pageTokenNoPage token, returned by a previous call, to request the next page of results.
filterNoAn expression for filtering the results. Syntax: "key:[<value>]". Available keys: owner, lastModified in ms (>lastModified). Multiple filters can be connected using a pipe |. Note that using different keys in the same filter results in "AND," while using the same key multiple times in the same filter results in "OR".
nameNoPartial name filter (case-insensitive). Returns only budgets whose name contains this string.
minCreationTimeNoMin value for budget creation time, in milliseconds since the POSIX epoch. Only budgets created after or at this timestamp are returned.
maxCreationTimeNoMax value for budget creation time, in milliseconds since the POSIX epoch. Only budgets created before or at this timestamp are returned.
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false. Description adds that it returns paginated results with specific fields. No contradictions; description enriches behavioral context without redundancy.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose and usage guidance, no fluff. Every sentence adds value.

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?

With no output schema, the description adequately summarizes return content (names, amounts, utilization). Parameters are fully described in schema, no gaps.

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

Parameters3/5

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

Schema description coverage is 100%; all parameters are documented in the schema. The description does not add extra parameter-level semantics beyond what the schema provides, meeting the 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?

The description states 'Use this when the user wants to see their cloud spending budgets or check budget status' and specifies it returns a paginated list with names, amounts, and utilization. This clearly distinguishes it from siblings like list_alerts and run_query.

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

Usage Guidelines5/5

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

Explicitly provides when to use (budgets, status) and when not to (cost analysis -> run_query, alerts -> list_alerts), offering clear alternatives.

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/doitintl/doit-mcp-server'

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