Skip to main content
Glama

Add to a savings goal

contribute_to_savings

Log an explicit savings contribution (CREDIT entry) against a savings goal. Commits immediately. amount_cents is MINOR units (cents): pass 10000 for 100.00, never a decimal. The returned amount is in currency units.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ledger_id": "<ledger_id>",
      "goal_id": "<goal_id>",
      "amount_cents": "<amount_cents>"
    },
    "name": "contribute_to_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYesId of the savings goal to contribute toward.
ledger_idYes
amount_centsYesContribution amount in minor units (cents). 10000 = 100.00.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world. The description adds material context beyond them: 'Commits immediately' tells the agent there is no draft/confirm step, which matters with confirm_change/discard_change siblings present. It also states the return unit convention, which annotations do not cover.

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?

Four short sentences, each earning its place: action, commit semantics, unit warning, return unit. The unit warning is front-loaded where an agent is most likely to err.

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?

With no output schema, the note that the returned amount is in currency units usefully prevents misreading the response. The only real gap is ledger_id semantics for a required parameter.

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 67%. The amount_cents unit rule is stated emphatically, but the schema already documents it (10000 = 100.00), so it is reinforcing rather than additive; the emphasis is still justified given the decimal-vs-cents footgun. ledger_id remains undocumented in both the schema and the description.

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?

CLEAR VERB+RESOURCE: 'Log an explicit savings contribution (CREDIT entry) against a savings goal.' The parenthetical names the ledger entry type, which distinguishes it from generic budget or expense tools. It does not explicitly contrast with a sibling, so it falls just short of 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?

'Explicit' hints that this is for manual contributions rather than automated transfers, which is implied usage guidance. There is no statement of when to prefer this over add_upcoming_expense or set_budget_goal, and no prerequisites or failure conditions are given.

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