Smart Expense Management MCP

by neev-25

Overview Schema Source Related Servers Discussions Admin

Python

Local

update_expense

Update specific fields of an expense using its ID. Modify only the details you need to change.

Instructions

Update specific fields of an expense. Only supply what you want to change.

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": {
      "expense_id": "<expense_id>"
    },
    "name": "update_expense"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`notes`	No
`title`	No
`amount`	No
`merchant`	No
`expense_id`	Yes
`category_id`	No
`expense_date`	No
`payment_method`	No
`subcategory_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'update', which implies mutation, but does not disclose authorization needs, side effects, or error handling (e.g., if expense_id does not exist).

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 a single sentence that front-loads the tool's purpose. Every word earns its place; there is no fluff.

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?

With an output schema present, return values are covered. However, the description lacks details about parameter constraints, validations, and behavioral expectations for a 10-parameter tool. It is insufficient for correct invocation without additional context.

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?

The description adds minimal meaning beyond the schema: 'Only supply what you want to change' indicates partial updates, but with 10 parameters and 0% schema coverage, the description should explain each field's purpose and format; it does not.

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 clearly states the verb 'update' and resource 'expense', distinguishing it from create/delete siblings. However, it lacks specificity about which fields are updatable, which is somewhat covered by the schema but not in the description.

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?

The phrase 'Only supply what you want to change' implies a partial update pattern, but there is no explicit guidance on when to use this tool versus alternatives like get_expense or create_expense. No prerequisites or exclusions are mentioned.

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