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

monarch-mcp2-obot

by dcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Merchants Update Merchant

merchants_update_merchant

Update a merchant's name or details in Monarch Money by specifying merchant_id. Changes apply to Monarch data, creating or updating records.

Instructions

Update merchant. This may create or update Monarch data.

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": {
      "merchant_id": "<merchant_id>"
    },
    "name": "merchants_update_merchant"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
merchant_idYes
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already convey that this is a mutating, open-world, non-idempotent operation. The description adds 'This may create or update Monarch data,' which hints at possible upsert behavior, but it remains too vague to clarify side effects, required auth, or what data may be created.

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 only two short sentences with the core action front-loaded. The second sentence is somewhat vague but does not add much length; overall it is concise and quickly scannable.

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 no output schema, the description leaves major questions open: what fields can be changed, whether it creates a merchant when absent, and what the response shape is. The annotations and schema provide structure, but the description alone is insufficient for reliable invocation.

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 does not mention any of the four parameters. Schema covers fields and output_mode with descriptions, but name and merchant_id have no descriptions, and the description adds no meaning to help an agent understand parameter constraints or relationships.

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?

'Update merchant' states a specific verb and resource, and the sibling set (list/get/delete) makes 'update' a distinct operation. The second sentence, 'may create or update Monarch data,' is vague but does not obscure the primary purpose.

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 gives no guidance on when to use this tool versus merchants_get_merchant, merchants_delete_merchant, or other merchant tools. It does not mention whether merchant_id must reference an existing merchant, any required permissions, or when the 'create' path applies.

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