Skip to main content
Glama
coolksrini

finpilot-mcp

by coolksrini

analyze_credit_report

Extract and analyze credit report data from CIBIL, Experian, or Equifax PDFs. Input file path and optional authentication details to unlock passwords.

Instructions

Analyze credit report from CIBIL, Experian, or Equifax.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dobNoDate of birth in DDMMYYYY format (e.g. "15081985") — used for password inference. CIBIL partner portals and Equifax use DOB directly as the password.
nameNoFirst name — used to auto-infer the password when not provided. CIBIL (mycibil.com): first 4 letters lowercase + birth year. Experian: first 4 letters uppercase + last 4 digits of mobile.
bureauNoCredit bureau name (cibil, experian, equifax) — auto-detected if not provided
mobileNo10-digit mobile number — last 4 digits used for Experian / CIBIL app format.
passwordNoPDF password if the file is password-protected.
file_pathYesPath or URL to the credit report PDF. Local path: /Users/name/Downloads/cibil_report.pdf Cloud URL: https://drive.google.com/... or https://1drv.ms/... (must be shared with "anyone with link can view")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states that the tool analyzes a report; it omits critical behaviors like password inference, bureau auto-detection, file format handling, or error conditions. The schema parameter descriptions hint at these details, but the main description fails to surface them.

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 with no waste. However, it is extremely terse, potentially sacrificing clarity for brevity. While it is well-structured and front-loaded, the lack of context prevents a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, password inference, multiple bureaus, output schema exists), the one-sentence description is insufficient. It does not explain auto-detection, password handling, or supported file sources, leaving the agent with limited guidance beyond the schema.

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 description coverage is 100%, with each parameter having a descriptive comment. The main description adds no parameter-specific information. Baseline 3 is appropriate since the schema already provides sufficient semantic context.

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 action ('Analyze'), the resource ('credit report'), and specifies the three supported bureaus (CIBIL, Experian, Equifax). This distinguishes it effectively from sibling tools like get_credit_health or analyze_portfolio, which target different financial functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, exclusions, or complementary tools. The sibling tools exist but are not referenced for differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/coolksrini/finpilot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server