Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_plan_settings

Read-only

Retrieve a YNAB plan's currency and date format settings to format amounts and dates correctly; omit the plan ID to use the configured default plan.

Instructions

Get a plan's currency and date format settings.

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

Input Schema

NameRequiredDescriptionDefault
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the scope of returned settings (currency and date format), with no mention of auth requirements, rate limits, or error behavior when the plan id is invalid.

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?

One short sentence with zero filler, leading directly with the verb and the two settings returned. Nothing is buried or redundant.

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 zero-required-parameter read tool with a fully documented schema and an output schema that carries the return shape, the description is nearly sufficient. The remaining gap is disambiguation from ynab_get_plan_overview, which shares the plan-level read domain.

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% and the single plan_id parameter already documents that it comes from ynab_list_plans and may be omitted for the configured default. The description adds no further meaning beyond the schema, so the baseline of 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?

States a specific verb ('Get') and resource ('a plan's currency and date format settings'), narrowing 'settings' to two concrete values. It does not differentiate from the nearby ynab_get_plan_overview, so an agent cannot tell from the description alone which one carries these fields.

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 tool reads plan-level configuration. There is no explicit guidance on when to call this versus ynab_get_plan_overview or ynab_list_plans, and no stated prerequisites beyond what the plan_id schema field implies.

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