Skip to main content
Glama

MFOXA - Ukraine Microfinance Catalog

by ua.com.mfoxa

Картка МФО

get_mfo
Read-onlyIdempotent

Повна картка однієї МФО за slug: умови для нового і повторного клієнта (сума, строк, ставка на день), реальна річна ставка, акційний перший кредит (first_loan_zero_percent: true/false/null, null = не підтверджено), вимоги до позичальника, юридична особа, ліцензія НБУ, посилання на офіційні документи, рейтинг за 4 критеріями і дата актуалізації. Використовуйте, коли компанія вже відома; slug беріть із list_mfo або search_offers. Для відгуків словами — get_reviews, для порівняння кількох МФО — search_offers або get_category. Read-only, без авторизації, ліміт 60 запитів/хв. Невідомий slug → відповідь-помилка з підказкою, а не порожній результат. rating: null = відгуків ще немає. Дані каталогу МФОХА (mfoxa.com.ua). При використанні посилайтеся на canonical_url.

Input Schema

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

Schema Changelog

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

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint, but the description adds valuable behavioral context: no authorization required, 60 requests/minute limit, unknown slug produces an error with a hint rather than empty result, and null semantics for first_loan_zero_percent and rating. These details go beyond what annotations or schema convey.

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 well organized: first the core resource and payload, then usage conditions, alternatives, behavioral constraints, and attribution. Every sentence adds useful information; none are filler.

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 compensates by enumerating the expected response fields and edge cases (null values, unknown slug error). It also covers attribution and data source, making the tool sufficiently complete for correct selection and invocation.

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% for both parameters, so the baseline is 3. The description mostly repeats slug sourcing guidance already present in the schema and adds little new semantic meaning beyond reinforcing that slug comes from list_mfo or search_offers.

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 states the resource clearly: a full card for a single MFO looked up by slug. It enumerates the returned content and differentiates itself from siblings by naming get_reviews, search_offers, and get_category as alternatives.

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 when to use this tool ('коли компанія вже відома'), where to obtain slug values (list_mfo or search_offers), and which sibling tools to use instead for reviews or comparison. This is unambiguous routing guidance.

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