Smart Expense Management MCP

by neev-25

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_subcategory

Add a subcategory to an existing category to organize expenses under specific labels.

Instructions

Add a subcategory to an existing category. Example: category_id=1, name='Biryani'

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": {
      "category_id": "<category_id>",
      "name": "<name>"
    },
    "name": "create_subcategory"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`category_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The description is minimal with no annotations. It states 'Add' implying a mutation but provides no details on side effects, required permissions, or reversibility. Without annotations, the description carries the full burden which is not met.

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

Conciseness4/5

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

The description is extremely concise with one sentence and an example. It is front-loaded with the purpose. However, it could be slightly more structured by separating the example from the main sentence.

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?

Given the tool has only 2 required parameters and an output schema, the description is adequate for a simple create operation. It does not fully leverage the context signals to add missing details, but it covers the essential information.

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 description coverage is 0%, and the description only mentions parameters via example. It does not explain valid values, constraints, or the meaning beyond their names. The example helps but does not compensate for the lack of schema descriptions.

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 action 'Add a subcategory' and the target resource 'to an existing category'. It distinguishes from sibling tools like create_category by explicitly referencing subcategory creation.

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?

Provides a concrete example (category_id=1, name='Biryani') which helps context. However, it does not explicitly state when to use this tool versus alternatives like create_category or update_category, nor does it mention any prerequisites or exclusions.

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