monarch-mcp2

Accounts Create Manual Account

accounts_create_manual_account

Create manual account. This may create or update Monarch data.

Instructions

Create manual account. 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": {
      "name": "<name>",
      "type": "<type>",
      "subtype": "<subtype>"
    },
    "name": "accounts_create_manual_account"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`type`	Yes
`fields`	No	Optional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
`balance`	No
`subtype`	Yes
`output_mode`	No	Output 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
`session_path`	No
`owner_user_id`	No
`include_in_net_worth`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, implying a safe write operation. However, the description adds the vague 'may create or update' without clarifying the exact behavior, authorization needs, or side effects. Beyond the annotations, the description offers minimal transparency.

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

Conciseness2/5

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

The description is too short to be effective; it omits essential context. The second sentence 'This may create or update Monarch data' adds confusion rather than value. A more structured, front-loaded description would better serve the agent.

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

Completeness1/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, low schema coverage), the description is vastly incomplete. It leaves the agent without understanding return values, required parameter relationships, or the difference between creation and update scenarios. The description fails to compensate for missing structured information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at only 22%, the description fails to explain the purpose or constraints of most parameters. It does not describe any parameter semantics beyond what is in the schema. The agent likely cannot infer correct usage for parameters like 'fields', 'balance', 'owner_user_id' etc.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create manual account' which identifies the action and resource, but the additional phrase 'This may create or update Monarch data' introduces ambiguity about whether this tool can also update existing accounts, which conflicts with the sibling tool 'accounts_update_account'. The purpose is partially clear but lacks precision.

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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives like 'accounts_update_account', nor does it explain prerequisites or consequences. The agent receives no context for tool selection.

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

Deploy Server