Skip to main content
Glama
klauern

MCP YNAB Server

by klauern

set_preference

Idempotent

Set and persist a user preference such as default budget ID, cache TTL, or confirmation flag to the preferences file.

Instructions

Set a single preference and persist it to preferences.json.

``name`` must be one of the ``Preferences`` model fields:
``default_budget_id``, ``category_cache_ttl_minutes``, or
``confirm_before_post``. Bool values accept any of
``1/0/true/false/yes/no/on/off`` (case-insensitive). The empty string is
the documented way to clear ``default_budget_id`` (stored as ``None``);
on a non-Optional field it surfaces as a coercion error.

Note: changes to ``default_budget_id`` here are equivalent to calling
``set_preferred_budget_id``; both write the same field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds behavioral details beyond annotations: persistence to file, empty string clearing behavior with storage as None, and coercion error on non-Optional fields. It also notes idempotentHint=true and that the tool is not read-only or destructive, which aligns with the description.

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?

The description is concise and well-structured: first sentence defines the main function, then a clear list of allowed names, followed by value format details and special cases. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given the presence of an output schema (not shown but known), the description adequately covers input semantics, edge cases (clearing, bool formats, errors), and comparison to a sibling tool. It provides sufficient context for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides only string types with no descriptions. The description enriches the semantics by listing the three valid names, specifying accepted bool values, and explaining the empty string clearing behavior. This fully compensates for the 0% schema coverage.

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

Purpose5/5

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

The description clearly states the tool sets a single preference and persists it to a file. It specifies the verb 'Set', resource 'a single preference', and target 'preferences.json'. It also distinguishes from the sibling tool set_preferred_budget_id by noting equivalence.

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

Usage Guidelines4/5

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

The description provides explicit allowed values for the name parameter (model fields), valid bool input formats, and how to clear a field. It mentions an alternative tool for setting default_budget_id. However, it could clarify when not to use this tool or when to prefer other siblings like get_preferences.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/klauern/mcp-ynab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server