Skip to main content
Glama
johannesbraeunig

ynab-mcp

Create a YNAB category

ynab_create_category

Add a new category to an existing YNAB category group, enabling better budget organization and spending tracking.

Instructions

Create a new category within an existing category group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new category
noteNoOptional note for the category
budget_idYesYNAB budget id, or "last-used" for the most recently used budget
category_group_idYesYNAB category group id the new category belongs to
Behavior3/5

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

Description aligns with annotations (readOnlyHint=false, openWorldHint=true, etc.) but adds no new behavioral details beyond what annotations provide.

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?

Single sentence, front-loaded, no unnecessary words.

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?

Description is sufficient for a simple create tool with thorough schema, but lacks mention of prerequisite that category group must exist.

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%, so parameters are well-described in schema. Description adds no extra parameter information.

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?

Description clearly states verb 'create', resource 'category', and location 'within an existing category group', distinguishing it from siblings like ynab_create_category_group or ynab_update_category.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives, no mention of prerequisites (e.g., category group must exist), and no when-not-to-use advice.

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/johannesbraeunig/ynab-mcp'

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