Skip to main content
Glama

Nubank 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.3/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. The description adds behavioral details: batch processing with `{ results, errors }` shape, and explains return content. No contradiction with 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?

The description is front-loaded with the core purpose. It lists many fields efficiently in parentheses without being overly verbose. Could be slightly more concise but overall well-structured.

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 1 parameter, no output schema, and good annotations, the description covers return shape, fields, and error handling. It is complete enough for a detail retrieval tool with clear guidance on prior steps.

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 1 required array parameter with 0% description coverage. The description adds meaning: 'Pass `loan_ids` as an array (1-50),' specifying size limit and batch context. This compensates well for the schema gap.

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 details by ID, listing many specific fields. It distinguishes from sibling 'openfinance_list_loans' by stating it is for deep-diving on a specific contract.

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 'Use after openfinance_list_loans to deep-dive on a specific contract.' Also specifies array size limits (1-50) and batch shape. No explicit when-not-to-use, but context is clear for a detail retrieval tool.

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

All Nubank 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 target distinct resource/action pairs, but there is real overlap among list_accounts, get_accounts_detail, and get_account_balance, as well as between list_transactions and list_transactions_by_item, and between get_credit_card_bill and list_credit_card_bills. The descriptions are detailed enough to usually resolve ambiguity, but the number of near-overlapping read/status tools makes mis-selection plausible.

Naming Consistency4/5

The 21 openfinance_* tools follow a clear openfinance_<verb>_<noun> convention with predictable verbs like list, get, update, force, disconnect, and search. The non-prefixed platform tools (authenticate, connect, marketlace, report_bug, show_version, toolkit_info) break the pattern but are few enough to keep the naming mostly coherent.

Tool Count3/5

25 tools is at the heavy end for the stated banking domain, and several could reasonably be merged: get_account_balance/get_accounts_detail/list_accounts and list_transactions/list_transactions_by_item overlap in purpose. The breadth of resources covered accounts, cards, loans, investments, connections, and provider health helps justify the count, but it still feels slightly bloated.

Completeness5/5

The Open Finance workflow is thoroughly covered: connect discover, force sync, status checks, accounts, balances, transactions, credit-card bills, loans, investments, category correction, disconnection, and provider health. Edge cases like stale data, consent errors, provider incidents, and cross-connector asymmetries are explicitly handled, leaving no obvious dead ends for an agent.

Resources