Skip to main content
Glama
drishit96

Budgetsco MCP Server

by drishit96

editRecurringTransaction

Update parameters of an existing recurring transaction, such as amount, frequency, category, or payment mode, to reflect changes in regular bills or income.

Instructions

Edit a recurring transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount of the recurring transaction
categoryYesCategory of the recurring transaction
descriptionNo
intervalYesInterval for the recurrence, for example, 1 for every day, 2 for every two months, etc.
occurrenceYesFrequency of the recurrence, for example, 'day' for daily, 'month' for monthly, 'year' for yearly
paymentModeYesPayment mode
startDateNoStart date of the recurring transaction. If not provided, it adds the transaction to the next occurrence based on the current date.
transactionIdNoId of the existing transaction. If creating a new transaction, this should be null or undefined.
typeYesType of the recurring transaction
Behavior2/5

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

Annotations already indicate readOnlyHint=false. The description adds no behavioral context beyond the mutation implication, such as effects on future occurrences or error handling.

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 a single, concise sentence. It is not verbose, but could benefit from slightly more context without becoming overly long.

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?

Given the tool's complexity (9 parameters, no output schema), the description lacks details on behavior (e.g., does it update future instances?) and return values.

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 description coverage is high (89%), and most parameters are explained there. The tool description adds no extra meaning beyond what the schema already provides.

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 'Edit a recurring transaction' clearly states the action and resource. It distinguishes from sibling tools like createRecurringTransaction and deleteRecurringTransaction.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. The schema's transactionId field implies it is for existing transactions, but no direct comparison or when-not advice is given.

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/drishit96/budgetsco-mcp-server'

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