Skip to main content
Glama
Sign In
Budgetsco MCP Server

Budgetsco MCP Server

by drishit96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Mark Recurring Transaction as Done

markRecurringTransactionDone

Mark a recurring transaction as completed for the current billing period. Provide the transaction ID to update its status and keep financial records accurate.

Instructions

Mark a recurring transaction as done for the current period

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": {
      "transactionId": "<transactionId>"
    },
    "name": "markRecurringTransactionDone"
  }
}

Input Schema

NameRequiredDescriptionDefault
transactionIdYesID of the recurring transaction to mark as done, skip or delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.8
    • removedInput schema / description
      Removed value: -"Parameters for marking a recurring transaction as done."
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate a non-read-only mutation, and the description adds the useful 'current period' scoping. However, it does not disclose what happens if the transaction is already done, whether the action can be reversed, or how 'done' differs behaviorally from 'skip'.

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 with no filler. The verb, object, and temporal scope are all front-loaded, and every word contributes to understanding the tool's action.

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

Completeness3/5

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

Given the tool has only one parameter and a straightforward action, the description is minimally usable. But it does not clarify the relationship to skipRecurringTransaction, nor what the practical effect of 'done' is, leaving some important context for the agent to infer.

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 100% for the single parameter, and the parameter itself is adequately described there. The tool description adds no additional meaning about transactionId, so it sits at the baseline for fully covered schemas.

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 uses a specific verb ('mark') and resource ('recurring transaction'), and adds the scope 'for the current period', which distinguishes it from delete or skip operations. It is clear but does not explicitly differentiate itself from the closely related sibling skipRecurringTransaction.

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 description provides no guidance on when to use this tool versus skipRecurringTransaction or deleteRecurringTransaction. The sibling list makes these alternatives obvious, but the description never states the condition that should select this one over them.

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

Deploy Server

Other Tools