Skip to main content
Glama
Zen Money MCP

Zen Money MCP

by bulava92

list_companies

Retrieve the banks and payment organizations available in Zen Money so you can identify financial institutions for transactions, accounts, or payment setup.

Instructions

Показать банки и платёжные организации из Дзен-мани.

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": "list_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 disclosure burden, and it supplies almost none: nothing says whether this is a safe read-only listing, whether results are cached or reflect the last sync, whether the list is complete or paginated. For a zero-parameter read tool the risk is low, but the description adds no behavioral context whatsoever beyond the resource name.

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?

One short sentence with no filler, and the resource is stated immediately. It is arguably too terse given everything left unsaid, but there is no wasted clause or repetition to penalize.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of information, yet it does not indicate what a returned company contains or how it relates to merchants, accounts, or transactions. For a trivial zero-param list tool this is minimally viable, but an agent gets no help deciding what to do with the results.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level value could be added here.

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?

Names a specific verb and resource: listing banks and payment organizations from ZenMoney. The resource is made concrete (banks/payment organizations rather than the vague 'companies' in the name), which helps an agent understand what entities come back. It stops short of differentiating itself from near-neighbours like list_merchants or list_instruments.

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 statement of when to call this instead of list_accounts, list_merchants, or get_zenmoney_entities, all of which live in the same sibling set. The agent must infer from the resource noun alone that this is the lookup for bank/payment-organization reference data. No prerequisites (e.g. prior sync) are mentioned.

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