Skip to main content
Glama

ASA 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

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds that it's a GET request and returns a batch shape, but does not describe error details or rate limits. No contradictions.

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?

Two sentences: first lists return fields, second gives usage and parameter constraint. No wasted words, well organized.

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?

Despite no output schema, the description enumerates key return fields (interestRates, charges, schedule, etc.) and batch shape, sufficient for an agent to understand the output fully.

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 has 0% description coverage for the lone parameter. Description adds that loan_ids is an array (1-50 items), which is critical usage detail beyond the schema's type definition.

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 the tool returns full loan contract detail by ID, listing many fields. It distinguishes from the sibling openfinance_list_loans by specifying it's for deep-diving into a specific contract after listing.

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 states 'Use after openfinance_list_loans to deep-dive on a specific contract' and specifies passing loan_ids as an array of 1-50 items. Also mentions batch shape with results and errors.

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

All ASA 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/5.0
Disambiguation3/5

The openfinance_* family is mostly well-differentiated by resource type, but several tools overlap in purpose: openfinance_get_account_balance, openfinance_get_accounts_detail, and openfinance_list_accounts all return account/balance data, and openfinance_list_transactions versus openfinance_list_transactions_by_item have similar scopes. The marketplace tool also bundles many sub-actions (search, invoke, install, subscribe, report_bug, prompt library) into one tool, and duplicates the standalone report_bug tool. Detailed descriptions help, but an agent could easily misselect among the account and transaction variants.

Naming Consistency4/5

Naming is largely consistent: the finance tools follow a clear openfinance_verb_noun pattern (list_accounts, get_account_balance, force_sync, update_transaction_category). There are minor singular/plural inconsistencies (get_account_balance vs get_accounts_detail, get_credit_card_bill vs list_credit_card_bills) and generic platform verbs like authenticate/connect/marketplace that follow a different style, but the overall pattern is predictable and readable.

Tool Count3/5

25 tools is at the upper boundary of what feels manageable for a server covering platform management, marketplace operations, and a broad Open Finance data domain. The count is defensible given the many resource types (accounts, transactions, bills, loans, investments, connections), but it is heavy and the marketplace tool alone packs a dozen sub-capabilities into one entry, making the surface feel larger than 25 discrete tools.

Completeness5/5

The Open Finance surface is quite complete: connection lifecycle (list, connect, disconnect, force sync, status, provider status), account and balance reads, transactions with categorization support, credit card bills with payment status, loans, investments, and investment transactions. Platform concerns like authentication, versioning, toolkit state, marketplace search/install/invoke, and bug reporting are also covered, leaving no obvious dead ends for the server's stated purpose.

Resources