Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

update_budget

Destructive

Modify an existing budget with partial updates. Adjust amount, currency, type, time interval, alerts, and more after user confirmation.

Instructions

Use this when the user wants to modify an existing budget. Supports partial updates. Ask the user to confirm the changes before executing. Do NOT use this for viewing budgets (use list_budgets) or creating new budgets (use create_budget).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBudget name. Must be non-empty if provided.
amountNoBudget period amount.
currencyNoCurrency code. Accepted values: USD, ILS, EUR, AUD, CAD, GBP, DKK, NOK, SEK, BRL, SGD, MXN, CHF, MYR, TWD, EGP, ZAR, JPY, IDR, AED, THB, COP.
typeNoBudget type. Accepted values: fixed, recurring.
timeIntervalNoRecurring budget interval. Accepted values: day, week, month, quarter, year.
startPeriodNoBudget start date as a UNIX timestamp in milliseconds.
endPeriodNoFixed budget end date as a UNIX timestamp in milliseconds. Must not be set for recurring budgets.
descriptionNoBudget description.
usePrevSpendNoUse the last period's spend as the target amount for recurring budgets. Defaults to false.
growthPerPeriodNoPeriodical growth percentage in recurring budgets. Must be >= 0. Defaults to 0.
metricNoBudget metric. Accepted values: cost, amortized_cost. Defaults to cost.
publicNoPublic sharing access level. Accepted values: owner, editor, viewer.
scopesNoFilters that define the scope of the budget. Cannot be combined with scope.
scopeNoList of allocations that define the budget scope (deprecated). Cannot be combined with scopes.
collaboratorsNoList of permitted users to view/edit the budget. If provided, must include at least one collaborator with role 'owner'.
alertsNoList of up to three alert thresholds defined as a percentage of the amount.
recipientsNoList of email addresses to notify when reaching an alert threshold.
recipientsSlackChannelsNoList of Slack channels to notify when reaching an alert threshold.
seasonalAmountsNoList of seasonal amounts for recurring budgets with different amounts per period.
idYesThe ID of the budget to update (required).
Behavior4/5

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

Annotations already provide readOnlyHint=false and destructiveHint=true. The description adds value by stating 'Supports partial updates' and requiring user confirmation, which is additional behavioral context. No contradiction, but could elaborate on side effects given openWorldHint=true.

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?

The description consists of three front-loaded sentences with no fluff. Each sentence serves a distinct purpose: stating the action, indicating partial updates, and providing usage guidance.

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

Completeness4/5

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

Given the complexity (20 parameters, 3 annotations, no output schema), the description adequately covers the tool's purpose and usage but does not mention the return value (e.g., updated budget object) or address side effects hinted by openWorldHint. It is mostly complete but has minor 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% for all 20 parameters, so the baseline is 3. The description does not add additional parameter details, but the schema already provides comprehensive descriptions.

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 clearly states 'modify an existing budget' and 'Supports partial updates,' providing a specific verb and resource. It distinguishes itself from sibling tools by explicitly mentioning not to use for viewing (list_budgets) or creating (create_budget).

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?

The description explicitly instructs when to use the tool (modify existing budget) and when not to (view or create). It also advises to ask the user to confirm changes before executing, providing clear usage guidance.

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