Skip to main content
Glama

Inferventis — Financial Data, News & Web MCP

by io.github.jonathanpchapman

bank_accounts

Retrieves bank account details and recent transaction history via a connected bank API integration. Returns a list of transactions for the specified account, or for all linked accounts when no account ID is provided. Use bank_accounts when an agent needs to inspect account balances, review recent spending, categorise transactions, or reconcile records against a specific bank account. Prefer open_banking_transactions when the integration uses a PSD2 Open Banking provider (TrueLayer) covering 300+ UK and European banks — open_banking_transactions returns richer transaction metadata including merchant names, categories, and running balances. Prefer stripe_payments when the source of payments is a Stripe merchant account rather than a retail bank account. This tool requires a valid bank API credential to be configured on the server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return. Defaults to 20. Maximum 100.
account_idNoIdentifier of the specific bank account to query. When omitted, transactions across all linked accounts are returned.

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains what is returned (list of transactions), how account filtering works, and the credential prerequisite. It doesn't cover edge behaviors like error handling or rate limits, but covers the core behavior well.

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 well-structured and front-loaded with the primary purpose. It includes essential context about alternatives and requirements without fluff. Every sentence contributes to understanding when and how to use the tool.

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 tool's simplicity (2 optional params, no output schema), the description is complete. It covers purpose, usage, alternatives, and prerequisites, making it sufficient for an agent to select and invoke correctly.

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 coverage is 100% for both parameters, so baseline is 3. The description adds value by explaining that omitting account_id returns transactions across all linked accounts and that limit controls the maximum number of transactions, reinforcing and extending the schema descriptions.

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 retrieves bank account details and transaction history, with a specific verb and resource. It also differentiates itself from siblings like open_banking_transactions and stripe_payments by specifying the connected bank API integration and scope.

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?

The description provides explicit usage guidance: 'Use bank_accounts when...' and 'Prefer open_banking_transactions when... / Prefer stripe_payments when...' It also notes the credential requirement, giving clear context for when to choose this tool over alternatives.

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

All Inferventis — Financial Data, News & Web 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

Many tools have overlapping purposes, especially in currency conversion (5 tools) and financial calculations (2 tools). While descriptions are detailed and try to differentiate, the sheer number of similar tools could confuse an agent. The platform_tool_finder tool helps but doesn't fully resolve ambiguity.

Naming Consistency3/5

Naming follows snake_case but is inconsistent: some tools use noun_verb (e.g., currency_convert), others noun_noun (e.g., bank_accounts). There are also variants with suffixes like '_lite' and '_open' which help, but the pattern varies across the set.

Tool Count4/5

20 tools is reasonable for a financial data and news server, covering stocks, crypto, fiat, banking, payments, calculations, and web content. However, there is redundancy (5 fiat converters) that could be streamlined, making the count slightly higher than ideal.

Completeness4/5

The tool set covers a broad range of financial tasks: real-time stocks, crypto, fiat conversion, bank transactions, payments, financial calculations, news, and web reading. Minor gaps exist, such as lack of historical stock data or portfolio tracking, but most common queries can be handled.

Resources