Skip to main content
Glama

Simple Interest

simple_interest_calculator
Read-onlyIdempotent

Interest on a fixed amount, without compounding. Same calculation as https://paisafinder.com/calculators/simple-interest-calculator. Every input is optional; anything left out uses the default shown in its schema.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "simple_interest_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoPrincipal (rupees)
rateNoRate (p.a.) (%)
yearsNoTime (years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuinely useful behavior beyond that: all inputs are optional and omitted values fall back to schema defaults. It does not disclose the shape or units of the returned result, which limits the added value to a 3.

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?

Two short sentences, front-loaded with the core definition, with no filler. The external URL is arguably inert for an agent since it cannot browse, but it is a single clause and does not distract from the key information.

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 three-parameter, no-required-input calculator with complete schema coverage and full annotations, the description covers purpose, the non-compounding model and default handling. What is missing is how the result is presented and in what units, plus explicit routing away from the compound-interest sibling.

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% and each parameter already carries a description, unit and min/max/default. The description's note that every input is optional and falls back to the default merely restates the schema's default values, adding no new meaning such as accepted ranges or rounding behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines the calculation precisely: 'Interest on a fixed amount, without compounding.' The phrase 'without compounding' implicitly separates it from the sibling compound_interest_calculator, but no sibling is actually named, so the differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied by the phrase 'without compounding', which suggests simple-interest scenarios rather than compound ones. There is no explicit 'use this when' statement and no named alternative for the compounding case, so an agent must infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources