Skip to main content
Glama
Zen Money MCP

Zen Money MCP

by bulava92

get_zenmoney_profile

Shows your Zen Money profile ID and primary currency so you can identify account settings and verify the currency used for financial tracking.

Instructions

Показать ID профиля и основную валюту Дзен-мани.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Показать' (show) implies a read-only operation and the description does state the returned content (ID, main currency), which is useful since there's no output schema. It still says nothing about authentication, API calls, or rate limits.

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

Conciseness5/5

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

A single front-loaded sentence with no wasted words. For a zero-parameter tool this is the right size.

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

Completeness4/5

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

Given no input schema, no output schema and no annotations, the description does the key remaining job: it tells the agent what comes back (profile ID and main currency). It does not mention the safety profile or call behavior, which are minor gaps for a simple read.

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, so the baseline is 4. Nothing in the description misleads about inputs.

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 names a specific verb and resource: showing the Zen-money profile, with the exact fields returned (profile ID and main currency). It's easy to distinguish from siblings like list_accounts or list_instruments, though 'profile' is not named as a scope contrast to those list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: it's a profile lookup, useful when the caller needs the account ID or base currency. There's no explicit statement of when to use it instead of list_accounts or other identity-providing calls, and no prerequisites are given.

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