Skip to main content
Glama

Подшито: инструменты юриста

Сумма прописью

amount_words
Read-onlyIdempotent

Сумма в рублях прописью для договора, иска или расписки: три привычных вида записи. Суммы — в рублях, даты — ГГГГ-ММ-ДД. Страница: https://podshito.ru/instrumenty/summa-propisyu/

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": {
      "amount": "<amount>"
    },
    "name": "amount_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesСумма. Рубли, копейки — дробной частью: 150000.5

Output Schema

NameRequiredDescriptionDefault
dataYes
linksNo
stepsYes
sourceYes
tablesYes
copyTextYes
dataAsOfNo
headlineYes
warningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description still adds value by disclosing that the result comes in 'три привычных вида записи' — an output-shape trait not present in the annotations, and it fixes the currency to rubles.

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 core purpose is front-loaded in one tight clause, and nothing is padded with marketing language. However, the sentence about date format 'ГГГГ-ММ-ДД' is dead weight for a tool with no date parameter, and the trailing page URL adds little for an invoking agent.

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 an output schema present, return values need not be spelled out, and the annotations plus a fully documented single parameter carry the rest. The definition is essentially sufficient; only the stray date-format note creates minor ambiguity about what this tool actually accepts.

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 100%: the single 'amount' parameter is already documented with range limits and a fractional-kopeck example (150000.5). The description only reinforces that sums are in rubles, which is a marginal addition over the schema text.

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 transformation (an amount rendered in words, in rubles) and its intended documents (contract, claim, receipt), plus that three standard output forms are produced. That is far more specific than the title alone, though it never contrasts itself with amount-adjacent siblings such as claim_price or state_fee.

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 context is implied by the phrase 'для договора, иска или расписки', which tells the agent the document scenarios where this applies. There is no explicit when-not guidance and no named alternative tool for related calculations, so selection still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources