FinanceGenius.AI

Explain a financial concept

explain_financial_concept

Read-only

Answer financial questions using FinMall.AI's hybrid knowledge base.

    Searches across product brochures, regulatory guides, calculators help,
    and live product database using BM25 + semantic + product DB search
    fused with Reciprocal Rank Fusion. Best for explainers like:
    'what is a critical illness rider?', 'how does APR work?',
    'difference between ELSS and PPF?'.

    Args:
        query: The financial question or concept to explain.
        institution: Optional — narrow search to one institution (e.g. 'hdfc-bank').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`institution`	No

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the tool read-only and non-destructive. The description adds meaningful behavioral detail: it searches across brochures, regulatory guides, calculator help, and a live product database using BM25, semantic search, and product DB search with Reciprocal Rank Fusion. This tells the agent the tool aggregates multiple sources rather than returning a single static answer.

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 well organized, front-loads the purpose, and includes useful examples and parameter documentation. The only slight inefficiency is the detailed search-algorithm explanation, which is informative but not strictly necessary for invoking the tool correctly.

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?

For a read-only question-answering tool with two simple parameters, the description covers purpose, examples, and parameter semantics. It does not describe the return format or whether results include citations, but with no output schema and a straightforward answering tool, the description is sufficiently complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden for parameters. It provides clear semantics for both: 'query: The financial question or concept to explain' and 'institution: Optional — narrow search to one institution (e.g. 'hdfc-bank')'. This goes well beyond the bare parameter names in the schema.

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 opens with a specific action—'Answer financial questions using FinMall.AI's hybrid knowledge base'—and provides concrete example queries ('what is a critical illness rider?', 'difference between ELSS and PPF?'). It clearly positions the tool as a conceptual explainer, which differentiates it from calculator, product lookup, and comparison siblings.

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 states this tool is 'Best for explainers' and gives representative examples covering definitions, calculations, and comparisons. It conveys when to use it, though it does not explicitly name sibling tools to avoid or say 'use search_indian_products instead for raw product searches.' The context is clear enough for an agent to route appropriately.

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

All FinanceGenius.AI tools Inspect

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

A4.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: the calculate_* tools cover different financial formulas, find_best_* tools recommend different product types, and search/get/compare form a coherent product workflow. There is no realistic ambiguity between tools despite the overlap in financial domain.

Naming Consistency5/5

Tool names consistently follow a verb-first snake_case pattern, with clear groupings like calculate_*, find_best_*, and get_*. Minor use of abbreviations like CAGR and EMI is natural and does not break the naming convention.

Tool Count5/5

12 tools is well-scoped for a personal finance assistant covering calculators, product search, product details, comparisons, recommendations, and concept explanations. Each tool earns its place without redundancy or bloat.

Completeness4/5

The tool set covers core financial calculations, product discovery, comparison, recommendations, and educational explanations, which is strong for the stated purpose. Minor gaps exist around loan/insurance product comparisons and more advanced investment planning, but agents can accomplish most typical finance workflows.

Resources

Need Help?