Skip to main content
Glama

MFOXA - Ukraine Microfinance Catalog

by ua.com.mfoxa

Відгуки про МФО

get_reviews
Read-onlyIdempotent

Останні відгуки позичальників про одну МФО за slug: оцінка 1–5, дата, текст, ім'я автора (лише те, що публічно на сайті) і total — загальна кількість відгуків. Використовуйте після get_mfo, коли потрібна думка клієнтів словами; для середньої оцінки достатньо get_mfo або list_mfo. Read-only, без авторизації, ліміт 60 запитів/хв. Повертає до limit найновіших (типово і максимум 10, без пагінації); МФО без відгуків → порожній список і total: 0; невідомий slug → відповідь-помилка з підказкою. Дані каталогу МФОХА (mfoxa.com.ua). При використанні посилайтеся на canonical_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoМова відповіді: uk (українська, типово) або ru. Змінює мову назв і текстів, а не набір данихuk
slugYesSlug МФО — латиниця, цифри, дефіси, як у list_mfo або в URL картки /mfo/{slug}, напр. credit7
limitNoСкільки найновіших відгуків повернути: 1–10, типово 10

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Мова відповіді: uk (українська, за замовчуванням) або ru"New value: +"Мова відповіді: uk (українська, типово) або ru. Змінює мову назв і текстів, а не набір даних"
    • addedInput schema / properties / limit / description
      Added value: +"Скільки найновіших відгуків повернути: 1–10, типово 10"
    • changedInput schema / properties / slug / description
      Previous value: -"Slug МФО"New value: +"Slug МФО — латиниця, цифри, дефіси, як у list_mfo або в URL картки /mfo/{slug}, напр. credit7"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior; the description additionally discloses no-auth requirements, rate limit of 60 req/min, no pagination with max 10 newest reviews, empty-list/total:0 edge cases, unknown-slug error behavior, data source, and canonical_url attribution requirement. 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?

The description is dense but every clause adds value: return contract, usage guidance, behavioral limits, edge cases, data source, and attribution. It is front-loaded with the core purpose and contains no redundancy with the schema or annotations.

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?

There is no output schema, but the description fully explains the returned fields, result limits, edge cases, rate limit, authorization, and relationship to sibling tools. An agent has all necessary information to select, call, and interpret the result of this tool correctly.

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 schema already documents all three parameters. The description adds operational semantics: slug is tied to list_mfo or the /mfo/{slug} URL, and limit is clarified as returning newest reviews with no pagination. Lang is not covered in the description, but the schema fully documents it.

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?

States a specific verb and resource: it returns the latest borrower reviews for one MFO by slug, and enumerates the returned fields (rating 1–5, date, text, author, total). It also differentiates itself from siblings by explicitly noting that get_mfo/list_mfo suffice for average ratings.

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?

Explicitly instructs to use this tool after get_mfo when qualitative customer opinions are needed, and says get_mfo or list_mfo is enough for average ratings. This gives clear when-to-use and when-not-to-use guidance relative to sibling tools.

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

All MFOXA - Ukraine Microfinance Catalog toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation4/5

Each tool targets a distinct resource or operation: list/get for categories and MFOs, search_offers for numeric matching, get_reviews for feedback, and get_market_rules for legal context. The only slight boundary is search_offers without filters returning the whole catalog, which overlaps list_mfo, but the descriptions explicitly cross-reference when to use each.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: get_* for single-item or static resources, list_* for enumerations, and search_offers for query-based selection. There are no style mixes or vague verbs.

Tool Count5/5

Seven tools is well-scoped for a read-only catalog: browsing lists, fetching details, searching offers, reading reviews, and accessing market rules. Each tool has a clear place and none feel redundant or missing enough to inflate the set.

Completeness4/5

The surface covers the core catalog journey: categories (list/get), MFOs (list/get), offers search, reviews, and legal context. Minor gaps include lack of a direct by-name MFO search and reviews limited to 10 recent items without pagination, but agents can work around these via list_mfo.

Resources