Skip to main content
Glama

get_budget

Read-only

Retrieve a wedding budget summary with total budgeted, actual cost, paid amounts, and item details; use brief view for one line per scheduled vendor payment and due status.

Instructions

Get the wedding budget summary including total budgeted, actual cost, paid, and all budget items

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
viewNo"full" (default) returns the usual JSON; "brief" returns one line per item: title — <ISO date or "no date"> — <status>. One line per scheduled vendor payment; the date is when it is due, status is paid or due.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the usual JSON; \"brief\" returns one line per item: title — <ISO date or \"no date\"> — <status>. One line per scheduled vendor payment; the date is when it is due, status is paid or due.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.4.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the response is a summary with four specific aggregates plus item-level detail, but it says nothing about the openWorld behavior, data freshness, or pagination/size limits. With annotations carrying the load, this is adequate but thin.

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?

A single front-loaded sentence with zero filler that leads with the action and then the returned content. Nothing is redundant or padded.

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 simple read-only tool with one optional enum parameter, no output schema, and rich annotations, the description covers what the tool retrieves. The only real omission is any reference to the view switch, which a caller would only find in the schema.

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% and the single optional 'view' enum is documented in detail in the schema, including the exact one-line brief format. The description does not mention 'view' at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 states a specific verb and resource ("Get the wedding budget summary") and enumerates what is returned: total budgeted, actual cost, paid, and all budget items. It is clearly a read operation distinct from the sibling update_budget_item, though it never names that sibling explicitly.

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 rather than stated: the agent can infer this is the retrieval tool for budget data while update_budget_item handles mutation. There is no explicit when-to-use framing, no mention of when a brief view is preferable, and no prerequisites or exclusions.

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