Skip to main content
Glama
Sign In
monarch-mcp2-obot

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Household Update Current User

household_update_current_user

Update the current user's profile data, such as timezone or display name, in Monarch Money. May create or update related Monarch records.

Instructions

Update current user. This may create or update Monarch data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "household_update_current_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
timezoneNo
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary
display_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the write behavior is known. The description adds only 'This may create or update Monarch data,' which is minimal but does not contradict the annotations and gives a slight behavioral hint. No contradiction detected.

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

Conciseness3/5

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

The desciption is very short and the main verb is front-loaded, but the second sentence is generic and does little work. It is concise more because it is under-specified than because every sentence earns its place.

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?

For a mutating tool with four parameters, no output schema, and openWorldHint=true, the description leaves important gaps: it does not say which user fields are updatable, what 'create' means in this context, or what side effects to expect. The schema and sibling list do not fill those gaps.

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 50: fields and output_mode have descriptions, but timezone and display_name do not. The tool description mentions no parameters at all, so it adds no semantic value beyond what the schema already provides and fails to compensate for the half-covered parameters.

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 states a specific verb and resource: 'Update current user.' It is clearly distinct from household_get_current_user on the read side, though it does not enumerate what fields can be updated or how it relates to household_update_household_preferences.

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?

There is no guidance on when to use this tool, when not to use it, or which sibling tool would be an alternative. The description only restates the action and adds a vague side-effect note, leaving the agent to infer appropriateness.

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