Skip to main content
Glama

Monte Bravo MCP

by io.github.mcp-dir

openfinance_get_accounts_detail

Read-onlyIdempotent

Returns full account objects including extended creditData (additional cards, limits) per id (GET /accounts/:id). Pass account_ids as an array (1–50). { results, errors } batch shape. May include a provider_incident block when the Open Finance provider has an OPEN incident affecting a connected bank: credit limits and balances may be unreliable (e.g. a limit near 1,00) until the provider recovers. Do not present those values as real.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idsYes

Schema Changelog

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

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds important behavioral context: batch response shape {results, errors}, and a provider_incident block that can make credit limits/balances unreliable. This adds value beyond annotations without contradiction.

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?

The description is three sentences with zero waste. First sentence states purpose, second gives parameter guidance, third warns about data reliability. Information is front-loaded and every sentence serves a distinct purpose.

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 the single parameter, clear annotations, and no output schema, the description covers the core functionality and a critical caveat. It does not detail the full return structure, but the warning about provider_incident is essential. Adequate for the tool's complexity.

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 has one parameter with 0% description coverage. The description explains it's an array of 1-50 items and implies they are account IDs (per id). It adds the batch response shape. However, it does not specify the format or type of the strings, leaving some ambiguity. Still, it compensates partially.

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 account objects with extended creditData per id. It specifies the endpoint and distinguishes from list accounts by highlighting detailed data. The verb 'Returns' and resource 'account objects' are specific.

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 explains to pass account_ids as an array (1-50) and describes batch shape. It provides a critical usage warning about provider_incident blocks. However, it does not explicitly state when to use this tool over siblings like openfinance_list_accounts, though the detail level is implied.

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

All Monte Bravo 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 openfinance_list_connections and openfinance_get_item_status overlap on connection status/reconnect URLs, and openfinance_list_transactions vs openfinance_list_transactions_by_item can be confused. The long descriptions reduce ambiguity, but selection risk remains.

Naming Consistency3/5

The openfinance_* block is consistently verb_noun, but the platform tools mix bare verbs (authenticate, connect), nouns (marketplace), and noun_info (toolkit_info). No single naming convention spans the whole set, though each subgroup is internally readable.

Tool Count3/5

At 25 tools, this sits at the top of the heavy borderline range. The broad scope—MCP.AI platform management, prompt library, and Open Finance data—justifies many tools, but the set feels like a bundled suite rather than a tightly scoped single-purpose server.

Completeness4/5

The Open Finance side is well covered: accounts, balances, transactions, credit card bills, loans, investments, connections, sync, status, provider health, and category updates. The platform side has auth, toolkit info, marketplace, and feedback. Minor gaps exist, such as no explicit identity fetch or payment initiation, but those seem outside the intended read/analysis domain.

Resources