catalog

Правовой контекст микрозаймов в России

get_market_rules

Read-onlyIdempotent

Возвращает справку по регулированию микрозаймов в России: предельная ставка 0,8% в день, лимит переплаты 100% по займам до года с 01.04.2026, законы 151-ФЗ и 353-ФЗ, самозапрет на кредиты, период охлаждения, права заёмщика при взыскании. Параметров нет. Ответ: JSON {country, reviewed_at (дата последней редакционной проверки правового блока), summary (краткий текст), details_markdown (полный блок в Markdown), source (URL первоисточника на zaimhub.com)}. Используйте для вопросов о законах, лимитах ставок и правах заёмщика; условия конкретных МФО — get_mfo, подбор предложений — search_offers. Правовые лимиты актуальны на reviewed_at. Только чтение, без авторизации и побочных эффектов и внешних сетевых вызовов; лимит 60 запросов в минуту с одного IP (при превышении HTTP 429).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`source`	Yes	Первоисточник — llms-full.txt на zaimhub.com
`country`	Yes
`summary`	Yes	Краткий правовой контекст
`reviewed_at`	Yes	Дата последней проверки правового блока, YYYY-MM-DD
`details_markdown`	Yes	Полный блок «Ключевые факты» в Markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "country": {
+      "type": "string"
+    },
+    "details_markdown": {
+      "description": "Полный блок «Ключевые факты» в Markdown",
+      "type": "string"
+    },
+    "reviewed_at": {
+      "description": "Дата последней проверки правового блока, YYYY-MM-DD",
+      "type": "string"
+    },
+    "source": {
+      "description": "Первоисточник — llms-full.txt на zaimhub.com",
+      "format": "uri",
+      "type": "string"
+    },
+    "summary": {
+      "description": "Краткий правовой контекст",
+      "type": "string"
+    }
+  },
+  "required": [
+    "country",
+    "reviewed_at",
+    "summary",
+    "details_markdown",
+    "source"
+  ],
+  "type": "object"
+}

First observedAug 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints, and the description goes beyond them by stating no authorization is needed, no side effects occur, no external network calls are made, and there is a 60 requests/minute rate limit with HTTP 429 on exceeding it. It also clarifies that legal limits are valid as of reviewed_at, adding temporal context. No contradiction with annotations.

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?

Every sentence delivers useful information: purpose, content scope, output format, usage guidance, alternatives, validity timing, and rate limit. The description is dense but not bloated, and the core purpose is front-loaded.

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

Completeness5/5

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

For a parameterless informational tool with an output schema and safety annotations, the description covers everything an agent needs: what data is returned, when to use it, how it differs from siblings, freshness of legal limits, and operational constraints like rate limiting. No significant gap remains.

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 has zero parameters and the schema is empty with 100% coverage, so parameter semantics barely apply. The description explicitly notes 'Параметров нет', which is sufficient; no additional parameter detail is necessary. The baseline of 4 for zero-parameter tools is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Возвращает справку по регулированию микрозаймов в России' — it says exactly what the tool returns and lists concrete content (rate cap, overpayment limit, laws, borrower rights). It also distinguishes itself from get_mfo and search_offers, making the tool's unique role clear.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool: 'Используйте для вопросов о законах, лимитах ставок и правах заёмщика'. It also names the alternatives for different cases: 'условия конкретных МФО — get_mfo, подбор предложений — search_offers'. This leaves no ambiguity about tool selection.

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

All catalog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.