catalog

Подбор предложений по сумме и сроку

search_offers

Read-onlyIdempotent

Подбирает предложения МФО для новых клиентов по сумме займа (amount, ₽), сроку (term_days, дней) и признаку первого займа под 0% (first_loan_zero: true — только МФО с беспроцентным первым займом). Все фильтры необязательны; без них возвращается весь каталог, поэтому задавайте amount и/или term_days и ограничивайте limit (по умолчанию 15, максимум 100). Результат отсортирован по месту в рейтинге заёмщиков. Ответ: JSON {query, total, truncated, note, offers[]}, у каждого предложения: name, slug, amount_range, term_range, rate, interest_free_days, first_loan_zero_percent (true/false/null, null — не подтверждено), rating_average, canonical_url. Используйте, когда у пользователя есть конкретная сумма или срок; весь каталог по рейтингу — list_mfo, тематические подборки (займ на карту, без отказа и т.п.) — list_categories и get_category, подробности по МФО — get_mfo. Только чтение, без авторизации и побочных эффектов; лимит 60 запросов в минуту с одного IP (при превышении HTTP 429). Условия волатильны — финальные смотрите на canonical_url.

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": "search_offers"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Сколько предложений вернуть, 1–100 (по умолчанию 15)
`amount`	No	Нужная сумма займа в рублях, например 15000
`term_days`	No	Нужный срок в днях, например 30
`first_loan_zero`	No	true — только МФО с первым займом под 0% для новых клиентов

Output Schema

Name	Required	Description
`note`	Yes
`query`	Yes	Применённые фильтры
`total`	Yes	Сколько предложений подошло всего
`offers`	Yes
`truncated`	Yes	true — вернулась не вся выборка, увеличьте limit

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- removedOutput schema / properties / offers / items / properties / first_loan_zero_percent / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / offers / items / properties / first_loan_zero_percent / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed5 schema fields changedSep 6, 2026

addedInput schema / properties / amount / description

Added value: +"Нужная сумма займа в рублях, например 15000"

addedInput schema / properties / first_loan_zero / description

Added value: +"true — только МФО с первым займом под 0% для новых клиентов"

addedInput schema / properties / limit / description

Added value: +"Сколько предложений вернуть, 1–100 (по умолчанию 15)"

addedInput schema / properties / term_days / description

Added value: +"Нужный срок в днях, например 30"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "offers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount_range": {
+            "type": "string"
+          },
+          "canonical_url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "first_loan_zero_percent": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "interest_free_days": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rate": {
+            "type": "string"
+          },
+          "rating_average": {
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "term_range": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "slug",
+          "canonical_url",
+          "first_loan_zero_percent"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "additionalProperties": false,
+      "description": "Применённые фильтры",
+      "properties": {
+        "amount": {
+          "type": "number"
+        },
+        "first_loan_zero": {
+          "type": "boolean"
+        },
+        "term_days": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "total": {
+      "description": "Сколько предложений подошло всего",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "true — вернулась не вся выборка, увеличьте limit",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "query",
+    "total",
+    "truncated",
+    "note",
+    "offers"
+  ],
+  "type": "object"
+}

First observedAug 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description still adds real context beyond them: no authorization required, a 60 requests/minute per-IP rate limit with HTTP 429 on breach, result ordering by borrower rating, and a caveat that terms are volatile and the canonical_url is authoritative.

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?

Front-loaded with purpose, then filters, then sibling routing, then behavior and response shape — a logical order with no filler sentences. It is dense and long for a four-parameter search tool, and the field-by-field enumeration of the response partly duplicates the output schema.

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?

Covers everything an agent needs for a low-complexity search: when to call it, what each filter means, default and max page size, ordering, rate limits, and how to verify volatile terms. Return fields are spelled out even though an output schema exists, so nothing material is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: currency and day units, the semantics of first_loan_zero=true, the default (15) and ceiling (100) of limit, and — most usefully — that omitting all filters returns the entire catalog. It mostly restates the schema's own parameter descriptions, which keeps it from a 5.

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 first sentence gives a specific verb and resource (selects MFO offers for new clients) and names the three filter axes with units. It is immediately distinguishable from list_mfo, list_categories, get_category and get_mfo, which are each named later with their own role.

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?

Explicit routing: use this when the user has a concrete amount or term; use list_mfo for the whole ranked catalog; use list_categories/get_category for thematic selections; use get_mfo for details on a single lender. It also states that all filters are optional and warns to constrain limit when omitting them.

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.