Zen Money MCP

create_merchant

Add a merchant to Zen Money so you can assign it to transactions and get matching suggestions.

Instructions

Добавить контрагента для операций и подсказок.

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": {
      "title": "<title>"
    },
    "name": "create_merchant"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation via "Добавить," but does not disclose permissions, duplicate handling, reversibility, or what the response contains.

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 a single short sentence with no obvious padding and front-loads the core action. Its brevity is appropriate, though it leaves much unsaid rather than being verbose.

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 creation tool with no annotations, no output schema, and no parameter descriptions, the definition is too thin. An agent lacks enough information about field semantics and creation side effects to invoke it confidently.

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?

There is one required parameter, "title," with 0% schema description coverage. The description does not explain what the title represents (e.g., merchant name), maximum length, or uniqueness expectations, so it fails to compensate for the missing schema documentation.

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 clear creation verb ("Добавить") and names the resource ("контрагента"), so an agent can understand this creates a merchant/counterparty. It also adds the purpose "для операций и подсказок," though it does not explicitly contrast with sibling tools like update_merchant or list_merchants.

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 phrase "для операций и подсказок" gives a broad use context, but there is no guidance on when to choose create_merchant versus update_merchant or list_merchants. No prerequisites or exclusions are stated.

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