Skip to main content
Glama

Banco Master 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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so description is consistent. It adds value by describing the batch processing and error shape beyond what annotations provide.

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?

Description is relatively concise and front-loaded with purpose. It lists many fields, which is helpful but slightly dense. Lacks markdown structure but still efficient.

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

Completeness4/5

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

Given single parameter, no output schema, and annotations covering safety, the description provides sufficient context: response shape, usage context, and parameter constraints. Could include more on error handling but adequate.

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 one param (loan_ids array), and description adds constraint 'as an array (1-50)', enhancing semantics beyond the schema. Schema coverage 0% but description compensates with this detail.

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, listing specific fields like interestRates, installments schedule, CET, etc. It also distinguishes from sibling openfinance_list_loans by saying 'Use after...'.

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 advises when to use this tool: after openfinance_list_loans to deep-dive on a contract. Also specifies batch usage with loan_ids array (1-50) and return shape `{ results, errors }`.

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

All Banco Master 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

A3.9/5.0
Disambiguation3/5

Most openfinance_* tools are clearly separated by resource and action, and the long descriptions help, but several pairs can trip up an agent: authenticate/connect both deal with login/connection state, openfinance_list_transactions and openfinance_list_transactions_by_item sound nearly identical, and marketplace internally exposes report_bug/list_tools functions that also exist as top-level tools. This is more than a single ambiguous edge.

Naming Consistency3/5

The 19 openfinance_* tools follow a clean get_/list_/update_ pattern and are easy to navigate, but the platform-level tools break the convention: authenticate, connect, marketplace, toolkit_info, report_bug, and show_version mix bare verbs, nouns, and noun-noun compounds. The pattern is not chaotic, but it is definitely mixed.

Tool Count3/5

25 tools is on the heavy end of the borderline range and is a large working set for an agent. The openfinance tools are individually justified and support batching, but the extra platform/marketplace tools add scope and some redundancy with report_bug and toolkit_info.

Completeness5/5

For a bank-data aggregation server, the surface is complete: connector discovery, linking/reconnecting/disconnecting, account lists and details, balances, transactions, categorization, credit-card bills, investments, loans, sync status, and provider health are all covered. There are no obvious dead ends in the main workflows.

Resources