Skip to main content
Glama

Méliuz 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

Schema Changelog

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

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint, covering safety. Description adds batch behavior ({ results, errors }) and array length limit, providing useful context beyond annotations.

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?

Two sentences front-load key info. Listing many fields may be slightly verbose, but each field adds value for an agent deciding to call this tool. Efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description must explain return shape. Lists many fields but lacks structured hierarchy or example. Adequate for a detail tool but not exhaustive.

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 coverage is 0%, so description must compensate. It explains loan_ids as an array (1-50) and mentions batch shape, but does not specify format of each ID (e.g., expected from list_loans). Adds some value but not fully explicit.

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?

Clearly states it returns full loan contract details by ID, listing specific fields. Distinguishes itself from sibling openfinance_list_loans by advising use after listing for deep-dive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use: after openfinance_list_loans. Provides batch shape and limit (1-50). Lacks explicit when-not or alternatives, but sibling context clarifies purpose.

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

All Méliuz 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.2/5.0
Disambiguation5/5

Each tool targets a distinct operation or data type (accounts, transactions, bills, loans, investments, connections, etc.) with no ambiguity. Even closely related tools like openfinance_list_transactions and openfinance_list_transactions_by_item are clearly differentiated by scope and output format.

Naming Consistency3/5

The majority of tools follow the 'openfinance_' prefix for banking operations, but utility tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) break this pattern, creating an inconsistent mix. However, the convention is still readable and the utilities are clearly distinct.

Tool Count4/5

25 tools is on the high side but well-justified by the breadth of Open Finance data types (accounts, transactions, credit cards, bills, loans, investments) and supporting operations (sync, status, search, updates). A few tools could potentially be merged, but overall the number is reasonable for the domain.

Completeness4/5

The tool surface covers the core Open Finance workflows: listing, reading details, syncing, updating categories, and checking provider status. Minor gaps exist (e.g., no tool to create or delete accounts/transactions), but these are external constraints. The set enables most user-facing financial queries and actions.

Resources