Skip to main content
Glama
Sign In
Personal Expenses MCP Server

Personal Expenses MCP Server

by gunnaabhinay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

initialize_new_month

Start a new monthly expense tracking period for a person, and prompt to confirm if their salary has changed for the new month.

Instructions

Initiates a new tracking month for a person. Explicitly prompts for whether their salary has updated for this new month.

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": {
      "name": "<name>",
      "month": "<month>",
      "has_salary_changed": "<has_salary_changed>"
    },
    "name": "initialize_new_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
monthYes
new_salary_amountNo
has_salary_changedYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 disclose side effects and permissions. It only mentions the prompting behavior for salary updates but does not state whether this is a write operation, what happens to existing data, or any prerequisites. This is a significant gap for a mutating tool.

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 concise with two compact sentences that avoid filler and redundancy. It directly states the primary action and one salient behavior. While more detail would be useful, the structure is clean and efficient.

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?

Although an output schema exists, the description lacks critical context about the tool's effects, parameter formats, and relationship to sibling tools. With no annotations and multiple parameters, the description is insufficient for an agent to invoke the tool correctly, especially regarding the salary-related parameters and side effects.

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%, so the description must compensate. It only hints at parameters (e.g., 'for a person' pointing to 'name', 'this new month' pointing to 'month') and implicitly references 'has_salary_changed' via 'salary has updated'. It does not explain the month format, the required boolean, or the meaning of 'new_salary_amount'.

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?

Uses a specific verb 'Initiates' with a clear resource 'a new tracking month for a person'. This distinguishes it from siblings like add_person or log_expense by its unique focus on month initialization, though it doesn't explicitly name alternatives.

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 implies this tool is used at the start of a new month for a person, but it does not explicitly say when to use it versus alternatives or any exclusions. The mention of prompting for salary changes gives some contextual clue but no explicit 'when-to-use' guidance.

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