Skip to main content
Glama

Neon 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.4/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds valuable behavioral details beyond annotations: batch shape ({ results, errors }) and array size limits. No contradiction.

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 a single sentence that front-loads the purpose and then lists key subfields. It is concise but could be slightly better structured (e.g., bullet points for fields). Still, it earns its place.

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 the complexity of a loan detail tool with many subfields and no output schema, the description clearly enumerates all major return fields (interestRates, contractedFinanceCharges, installment schedule, CET, etc.) and explains the batch shape. It is comprehensive for an AI agent.

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 description coverage is 0%, so the description must compensate. It does so by specifying that loan_ids is an array of 1-50 items and mentioning the batch result shape. This adds meaningful usage guidance beyond the schema 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 details by ID, enumerating specific fields (interestRates[], etc.). It distinguishes from sibling tools by explicitly recommending use after openfinance_list_loans 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?

The description explicitly advises using this tool after openfinance_list_loans and provides constraints on the loan_ids array (1-50). It does not list when-not-to-use or alternatives but gives clear context.

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

All Neon 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
Disambiguation4/5

The openfinance_* family is cleanly separated by resource and action, and tricky pairs like list_accounts vs get_account_balance and list_transactions vs list_transactions_by_item are explicitly cross-referenced in descriptions. However, marketplace bundles a large set of sub-actions, and connect/toolkit_info partially overlap on reporting connection state, so a couple of boundaries are fuzzy.

Naming Consistency4/5

The openfinance_* tools consistently follow a verb_resource pattern with snake_case, which is highly predictable. The generic platform tools mostly fit the same style, but marketplace and toolkit_info are noun-only names, and openfinance_provider_status also breaks the verb pattern, so it is not perfectly uniform.

Tool Count3/5

At 25 tools, this server falls at the heavy end of the borderline range. The many openfinance_* list/get tools are individually justified for the financial domain, but adding platform tools like marketplace, connect, toolkit_info, and show_version makes the overall surface larger than a minimal server needs.

Completeness5/5

The financial surface is remarkably thorough: accounts, transactions, credit card bills, loans, investments, categories, connection lifecycle, sync, and provider health are all covered with list/get and update paths where applicable. The platform side also covers auth, connection status, marketplace discovery/execution, versioning, and bug reporting, leaving no obvious dead ends.

Resources