Skip to main content
Glama
dannyshaw

Pocketsmith MCP Server

by dannyshaw

pocketsmith_create_category

Create a new category to organize your finances. Set a title, choose a color, and optionally assign a parent category, mark as transfer or bill, enable roll-up, and define refund behavior.

Instructions

Create a new category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe category title
colourNoThe category color in hex format (e.g., #FF0000)
parent_idNoParent category ID for creating a subcategory
is_transferNoWhether this category represents a transfer
is_billNoWhether this category represents a bill
roll_upNoWhether to roll up child categories
refund_behaviourNoHow refunds should be handled
Behavior1/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states 'Create a new category' without any details on side effects, authentication needs, idempotency, or error behavior. This is a significant gap.

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

Conciseness2/5

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

The description is extremely concise (one sentence), but this brevity sacrifices necessary information. It is under-specified for a tool with multiple parameters and no annotations, making it insufficient rather than appropriately concise.

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

Completeness1/5

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

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is severely lacking. It omits return values, error scenarios, and behavioral constraints, leaving the agent with minimal context for correct usage.

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?

The input schema has 100% coverage of its 7 parameters with descriptions. The description adds no additional meaning beyond the schema, so the baseline score of 3 applies. No extra context is provided for parameter usage.

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?

The description 'Create a new category' clearly states the verb (create) and resource (category). It is straightforward and adequately conveys the main action, though it does not differentiate from sibling tools like 'pocketsmith_create_category_rule'.

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 is provided on when to use this tool versus alternatives such as 'pocketsmith_list_categories' or 'pocketsmith_create_category_rule'. There is no mention of prerequisites, context, or exclusions.

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/dannyshaw/pocketsmith-mcp'

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