Skip to main content
Glama

My Budget Control

View MBC budget

get_budget
Read-only

Read income and expense totals for one MBC budget month. Does not move money or provide a verified bank balance.

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

Input Schema

NameRequiredDescriptionDefault
monthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so 'does not move money' largely restates structured data. The one genuinely additive statement is that the result is not a verified bank balance, which warns the agent about data trustworthiness. Return shape is only sketched as 'income and expense totals', with no pagination, defaults, or error behavior.

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 short sentences with zero waste: the core action first, then the two scope exclusions. Nothing is padded or repeated.

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?

For a single-parameter read tool with full annotation coverage and no output schema, the description is largely sufficient: it names the returned data and warns against treating it as a bank balance. The remaining gap is the default behavior for the optional month parameter, which an agent would need before calling it without arguments.

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?

There is one optional parameter at 0% schema description coverage, so the description must carry some burden. 'One MBC budget month' does clarify that the month parameter selects a budget month, but the description never states the accepted format (the schema only encodes it as a regex pattern) or what happens when month is omitted, which matters since it is not required.

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?

The description gives a specific verb and resource: 'Read income and expense totals for one MBC budget month.' An agent can tell this is a budget-reading tool. It stops short of distinguishing itself by name from the sibling tools (expense_status, prepare_expense), so a 4 rather than a 5.

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 only implied. The negatives ('does not move money', 'does not provide a verified bank balance') hint at when not to rely on this tool, but no alternative is named and no condition is stated for choosing it over expense_status or prepare_expense.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources