Skip to main content
Glama
Sign In
wallos-mcp

wallos-mcp

by LovelessCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update budgets

update_budget
Idempotent

Set a monthly budget or a weekly, fortnightly, or monthly rolling-period budget with an anchor date, so Wallos tracks spending against the correct cycle.

Instructions

Sets the monthly budget, or the budget for a rolling period such as weekly, fortnightly or monthly, with an anchor date that decides where periods begin.

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": "update_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
period_budgetNoBudget for one budget period.
monthly_budgetNoBudget for the month, in the main currency.
budget_period_typeNoLength of the budget period.
budget_period_anchor_dateNoYYYY-MM-DD date that periods are anchored to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare idempotent, non-destructive, openWorld and write behavior. The description adds only the anchor-date semantics and does not clarify the key behavioral ambiguity: how monthly_budget relates to period_budget + budget_period_type='monthly', whether they are mutually exclusive, or what happens when both/none are supplied (0 required parameters).

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

Conciseness3/5

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

A single front-loaded sentence with no padding, which is good, but the phrasing is muddled: 'monthly' appears both as the default case and inside the rolling-period list, muddying the enum mapping.

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

Completeness2/5

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

For a write tool with zero required parameters, no output schema, and two overlapping budget fields, the description should specify valid parameter combinations and the effect of an update. It leaves the agent to guess, which risks incorrect invocation.

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 coverage is 100%, so the parameters are already documented. The description adds one useful gloss — the anchor date decides where periods begin — but does not explain why two budget fields exist or how they interact, which is exactly the gap the schema leaves.

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

Purpose4/5

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

Names a specific verb and resource ('sets the monthly budget') and covers the period variants, so an agent knows it is a budget-write tool. It does not distinguish itself from siblings such as get_period_budget or get_monthly_cost, leaving the read-vs-write distinction to the name alone.

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

Usage Guidelines2/5

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

No statement of when to use this instead of the budget-reading siblings (get_period_budget, get_monthly_cost) or of prerequisites. The only usage hint is implicit: that a rolling period can be configured.

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