Skip to main content
Glama
Sign In
drebedengi-mcp

drebedengi-mcp

by hawk911
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Валюты

list_currencies
Read-only

Retrieve user currencies and their exchange rates to the base currency for accounting calculations and reports.

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_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read. The description contributes one useful behavioral fact beyond that: the returned rates are expressed relative to the main currency. It says nothing about freshness of the rates, whether all currencies or only held ones are returned, or ordering.

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 short sentence with no filler, and the key qualifier (rates to the main currency) is placed where it is read immediately. It is efficient, though so terse that it borders on under-specified rather than optimally structured.

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?

With zero parameters and no output schema, little is required of the description. It does state the shape of the result (currencies plus their rates against the main currency), which compensates for the missing output schema. Only freshness and scope (all currencies versus held currencies) remain unexplained.

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 there is nothing for the description to clarify beyond what the empty schema already shows. Baseline 4 applies. The description does not incorrectly suggest any filter arguments, which keeps the description consistent with the schema.

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?

"Валюты пользователя с курсами к основной валюте" states the resource (the user's currencies) and the content returned (rates against the main currency), which goes beyond the bare tool name. However, it is a noun phrase with no verb, and it does not distinguish itself from siblings such as add_currency_exchange or get_balance, so the agent must infer that this is a read/list operation from the name alone.

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 guidance, no mention of alternatives, and no preconditions. The agent gets no signal about whether this should be preferred over get_balance or add_currency_exchange when it needs currency-rate information.

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