Skip to main content
Glama

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

QR-код для оплаты по реквизитам

payment_qr
Read-onlyIdempotent

Платёжный QR-код по ГОСТ Р 56042-2014 для счёта, претензии или расписки: банк клиента сам подставит реквизиты и сумму. Нормы: ГОСТ Р 56042-2014. Суммы — в рублях, даты — ГГГГ-ММ-ДД. Страница: https://podshito.ru/instrumenty/qr-kod-dlya-oplaty/

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": {
      "name": "<name>",
      "bankAccount": "<bankAccount>",
      "bik": "<bik>",
      "bankName": "<bankName>",
      "sum": "<sum>",
      "purpose": "<purpose>"
    },
    "name": "payment_qr"
  }
}

Input Schema

NameRequiredDescriptionDefault
bikYesБИК банка
innNoИНН получателя
kppNoКПП
sumYesСумма. Рубли, копейки — дробной частью: 150000.5
nameYesПолучатель. Как в банке, например «ООО "Ромашка"».
purposeYesНазначение платежа
bankNameYesБанк
bankAccountYesРасчётный счёт
corrAccountNoКорреспондентский счёт

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful domain behavior — compliance with GOST R 56042-2014, ruble-only amounts, and YYYY-MM-DD dates — but says nothing about failure modes for invalid BIK/account data or what the caller receives.

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 dense sentence plus two short clarifiers; the deliverable and its purpose are front-loaded before the standard and format notes. The trailing page URL is extraneous for tool invocation but short enough not to harm readability.

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?

For a 9-parameter, 6-required generation tool with a full output schema and full annotation coverage, the description supplies the standard, currency, and date-format context that the schema alone does not. Only minor gaps remain, such as expected input validation behavior and the output representation.

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 description coverage is 100%, so every parameter, including the sum's kopeck-as-fraction format and name's bank-format requirement, is already documented. The description's currency and date-format notes add only marginal meaning beyond the schema, matching the baseline 3 for a fully documented schema.

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 concrete deliverable — a payment QR code per GOST R 56042-2014 — and scopes its use to invoices, claims, and receipts, adding that the payer's bank auto-fills the requisites and the amount. This is specific enough to distinguish it from calculator siblings, though it never states the action as an explicit verb ("сформировать/создать").

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?

Intended situations are implied by the enumeration of documents (счёт, претензия, расписка), so an agent can infer when the tool applies. However, there is no explicit when-to-use or when-not guidance, no prerequisites (e.g. required bank details), and no reference to any alternative tool such as requisites_check.

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