Skip to main content
Glama
Sign In
drebedengi-mcp

drebedengi-mcp

by hawk911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Обмен валюты

add_currency_exchange

Record a currency exchange transaction by specifying the sold amount and currency, the received amount and currency, and the source account.

Instructions

Обмен валюты: продано from_amount в from_currency, получено to_amount в to_currency.

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": {
      "from_amount": "<from_amount>",
      "from_currency": "<from_currency>",
      "to_amount": "<to_amount>",
      "to_currency": "<to_currency>",
      "account": "<account>"
    },
    "name": "add_currency_exchange"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoДата YYYY-MM-DD или YYYY-MM-DD HH:mm (по умолчанию — сейчас)
accountYesСчёт, с которого списана исходная валюта
commentNo
to_amountYes
to_accountNoСчёт, куда зачислена новая валюта (по умолчанию тот же)
from_amountYes
to_currencyYes
from_currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It only restates the amount/currency pairing and never says that this is a mutating operation, whether it affects account balances or exchange rates, whether the rate is derived from the two amounts, or what happens when to_account is omitted.

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?

A single compact sentence with the operation front-loaded and zero filler. It is efficient, though its brevity borders on under-specification for an 8-parameter mutation tool rather than being genuinely well-proportioned.

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 mutation tool with no annotations, no output schema, 8 parameters and only 38% schema coverage, the description is far too thin. Essential context — balance effects, default to_account behavior, and the absence of an explicit exchange rate parameter — is missing entirely.

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

Parameters3/5

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

Schema coverage is only 38% across 8 parameters, so the description must compensate. It does add real meaning for the four core parameters by fixing the direction semantics (from = sold/outgoing, to = received/incoming), but it says nothing about account vs to_account, date format, or comment, leaving half the surface undocumented in both places.

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 states a specific operation — recording a currency exchange, with the sold currency amount and the received currency amount named explicitly. It differentiates this from plain transfers only implicitly (the word 'exchange' plus two currencies), and never names add_transfer or add_expense as alternatives, so it stops short of full sibling differentiation.

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 when-to-use or when-not-to-use guidance at all. With siblings add_transfer, add_expense and add_income present, the agent gets no rule for choosing an exchange record over a two-legged transfer, and no prerequisite or duplicate-handling hints.

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