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

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

simple_interest_calc

Calculate simple interest by multiplying principal amount, annual interest rate, and time in years.

Instructions

Calculate simple interest: interest = principal × rate × time.

Parameters:
    principal — Principal amount.
    rate — Annual interest rate (e.g. 5.0 for 5%).
    time — Time period in years.

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>",
      "time": "<time>"
    },
    "name": "simple_interest_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
principalYes
rateYes
timeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description only gives the formula without disclosing any behavioral traits such as rounding, precision, or error handling. It does not add value beyond the basic calculation.

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 formula and parameter list. It is front-loaded with the purpose. However, it could be better structured, e.g., separating the formula from parameter descriptions.

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?

Given the tool's simplicity and the presence of an output schema (not shown but indicated), the description adequately covers the input parameters. It does not need to explain return values. Some additional behavioral context would be beneficial.

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?

The description adds meaningful context to each parameter: 'Annual interest rate (e.g. 5.0 for 5%)' and 'Time period in years'. With 0% schema description coverage, this compensation is good, though more detail on units or constraints could be added.

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 purpose: 'Calculate simple interest' with the formula provided. It distinguishes itself from sibling tools like compound_interest and amortization_calc implicitly by specifying the simple interest calculation.

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?

No explicit guidance on when to use this tool versus alternatives like compound interest or loan calculators. The description implies its use for basic interest calculation but does not mention exclusions or context.

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