Skip to main content
Glama

NSC Calculator

nsc_calculator
Read-onlyIdempotent

Post Office savings certificate: what your money becomes in 5 years. Same calculation as https://paisafinder.com/calculators/nsc-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": "nsc_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
amtNoInvestment (rupees)
rateNoCurrent NSC rate (p.a.) (%). Govt revises quarterly

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 covered and the description only needs to add context. It adds the fixed five-year horizon and the default-fill behavior for omitted inputs, but says nothing about what the response contains (maturity value, interest breakdown) despite having no output schema.

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 purpose before the optionality note. The reference URL is mildly promotional but does convey the exact calculation convention, so no sentence is wasted outright.

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 two-optional-parameter, read-only calculator with full schema coverage, the definition supplies horizon, optionality and default behavior — enough to invoke it correctly. The only real gap is the absence of any statement about the return value, which no output schema covers.

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 both parameters carry units, ranges and defaults, so the schema does the heavy lifting. The description's contribution — that omitted inputs fall back to those defaults — reinforces rather than extends what the schema already states.

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 names the specific instrument (Post Office savings certificate) and the exact projection it performs — 'what your money becomes in 5 years' — which separates it from PPF, FD and other savings siblings without ambiguity. It stops short of an explicit verb-plus-resource phrasing but the scope is unmistakable.

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 context is implied by the five-year NSC framing, and the description adds a genuinely useful rule that every input is optional with schema defaults. It never says when to prefer this over ppf_calculator or compound_interest_calculator, so selection guidance remains inference-based.

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