Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Createcategorygroup

createCategoryGroup

Creates a new category group in a YNAB plan by providing a plan ID and group name, helping organize budget categories.

Instructions

Creates a new category group

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": {
      "plan_id": "<plan_id>",
      "category_group": "<category_group>"
    },
    "name": "createCategoryGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan ("last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan)
category_groupYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare mutation. It does not say whether the group name must be unique, what happens on duplicate names, what the response contains (e.g., the new group id), or what authorization/plan scope is required for this write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single economical sentence with no wasted words, but its brevity comes from under-specification rather than tightness — there is no front-loaded detail beyond restating the name.

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

Completeness2/5

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

For a mutation tool with a nested object parameter, no annotations, and no output schema, this is too thin: the agent gets no return-value expectation, no error/precondition behavior, and no hint about how the created group relates to the plan.

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

Parameters2/5

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

Schema coverage is only 50%, so the description should compensate, but it says nothing about parameters. The schema itself documents plan_id's 'last-used'/'default' sentinels and the 50-character name limit, none of which the description reinforces or clarifies.

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

Purpose3/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 ('Creates a new category group'), so an agent knows the operation is a create on a category group. However, it is essentially an expansion of the tool name with no differentiation from near siblings such as updateCategoryGroup or createCategory, so it lands at minimum viable rather than clearly distinguishing.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., that a valid plan_id is required), and no indication of when to prefer updateCategoryGroup or createCategory instead. The agent must infer all of this from the name and schema.

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