Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

emi_calc

Calculate equated monthly installment (EMI) for loans using principal, annual interest rate, and tenure in months.

Instructions

Calculate Equated Monthly Installment (EMI) for loans.

Parameters:
    principal — Loan principal amount.
    rate — Annual interest rate (e.g. 8.5 for 8.5%).
    tenure_months — Loan tenure in months.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "principal": "<principal>",
      "rate": "<rate>",
      "tenure_months": "<tenure_months>"
    },
    "name": "emi_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
principalYes
rateYes
tenure_monthsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

B3.4/5.0
Behavior3/5

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

The description clarifies the input parameters (e.g., annual interest rate example) but does not mention output format, rounding, or precision. Since annotations are absent, the description bears full responsibility, but it provides only basic parameter details without deeper behavioral context.

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 concise with a clear opening sentence and a parameter list. It is front-loaded with the purpose and avoids unnecessary words. The parameter list is slightly redundant with the schema but adds brief clarification.

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

Completeness3/5

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

Given the tool's simplicity and the presence of a full input schema and output schema (though not shown), the description sufficiently explains the calculation purpose. However, it omits details about the output and fails to differentiate usage from similar siblings, leaving some gaps.

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 0%, so the description must compensate. It adds value for the 'rate' parameter by providing an example format ('e.g. 8.5 for 8.5%'), but for 'principal' and 'tenure_months', it merely restates schema titles. This marginal addition keeps it at a baseline of 3.

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 calculates Equated Monthly Installments for loans, which is a specific verb+resource. Among siblings like 'loan_calculator' and 'mortgage_calculator', it uniquely focuses on EMI, so it is well-distinguished.

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?

No guidance is provided on when to use this tool versus alternative finance calculators like 'loan_calculator' or 'compound_interest'. The description lacks context for selection and does not mention exclusions or prerequisites.

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

Deploy Server

Other Tools