Skip to main content
Glama

99Pay MCP

by io.github.mcp-dir

openfinance_get_loan_detail

Read-onlyIdempotent

Returns full loan contract detail by id (GET /loans/:loanId): interestRates[] (taxType, ratePercentage, indexer), contractedFinanceCharges[], balloonPayments[], warranties[], installments schedule (installmentsCount, paidInstallments, numberOfInstallmentsRemaining, installmentFrequency), amortizationScheduled, CET, ipocCode and dates. Use after openfinance_list_loans to deep-dive on a specific contract. Pass loan_ids as an array (1-50). { results, errors } batch shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loan_idsYes

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent), the description adds details on return field structure, batch error handling, and parameter limits, enhancing transparency.

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?

Three focused sentences: first covers purpose and returns, second usage context, third parameter and output shape. No redundancy, efficiently 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?

Given no output schema and moderate complexity, the description covers return fields, usage positioning, parameter constraints, and output shape. Adequately complete for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by specifying the array size limit (1-50) and clarifying batch semantics, adding significant meaning beyond raw schema.

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 clearly states it returns full loan contract detail by ID, lists key fields, and explicitly distinguishes itself from the sibling openfinance_list_loans by suggesting use after that.

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?

It explicitly instructs to use after openfinance_list_loans for deep-dive, specifies parameter constraints (array of 1-50 IDs), and mentions batch result shape, providing clear when and how.

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

All 99Pay MCP 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.4/5.0
Disambiguation5/5

Each tool targets a distinct resource and action, with clear separation between general server utilities (authenticate, connect, marketplace) and the openfinance_* family (get/list/search/update per domain). No two tools appear to overlap: list_transactions vs list_transactions_by_item are differentiated by granularity, and get_item_status vs provider_status by scope. The marketplace tool, while broad, is explicitly named and described, so it doesn't cause ambiguity.

Naming Consistency5/5

All 20 openfinance_* tools follow a strict verb_noun snake_case pattern (list_accounts, get_account_balance, force_sync, update_transaction_category, etc.). The five general tools also use snake_case and clear names, maintaining consistency across the set. No mixing of conventions or inconsistent verb styles.

Tool Count4/5

At 25 tools, the set is on the higher end but well-justified for a platform that aggregates Open Finance data and provides a marketplace. The 20 openfinance tools cover distinct banking operations (accounts, transactions, bills, loans, investments, connections, sync, status, search, categories), each addressing a specific need. The 5 general tools handle authentication, connection status, and platform info. No obvious trivial or redundant tools; each earns its place.

Completeness5/5

The tool surface is comprehensive for the stated domain: CRUD-like coverage across financial resources (list/get for accounts, transactions, bills, loans, investments), plus state management (force_sync, disconnect, update_category) and ecosystem support (search_connectors, provider_status, marketplace). It also includes utilities like authenticate, connect, and version/bug reporting. No missing operations that would cause agent failures; the set covers connection lifecycle, data retrieval, and even API diagnostics.

Resources