Skip to main content
Glama

India Salary Calculator

India: what these calculators cover

tax_rules_covered
Read-onlyIdempotent

The India rules the calculators apply (2026), the options they take, what is not modelled, and the official sources, for the salary calculators and the full income tax return. Call it before answering a question the other tools may not cover.

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": "tax_rules_covered"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral content: it is a static 2026 reference that includes negative scope ('what is not modelled') and provenance ('official sources'), which tells the agent to expect caveats and citations rather than computed numbers.

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?

A single front-loaded sentence that enumerates its content areas before the closing instruction on when to call it. It is slightly run-on and the trailing 'Call it before...' would land harder if split out, but no wording is wasted.

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?

There is no output schema, so the description must convey what comes back, and it does: applied rules, available options, non-modelled areas, and official sources. For a parameterless static reference tool this is close to complete; only the return shape (prose vs. structured list) is left unspecified.

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 tool takes zero parameters, so the baseline is 4. The description correctly offers no parameter guidance, and the empty schema is consistent with a parameterless reference lookup.

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 resource precisely: the India rules the calculators apply for 2026, the options they take, what is not modelled, and the official sources, scoped to the salary calculators and the full income tax return. It is a noun phrase rather than a verb+object, but an agent can still tell this is a documentation/coverage reference rather than a calculation, which separates it from the calculating siblings.

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

Usage Guidelines4/5

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

It gives an explicit trigger: call it before answering a question the other tools may not cover, which positions it as a pre-flight coverage check ahead of income_tax_return, net_salary, and the rest. It does not state when to skip it (e.g. for straightforward calculations the siblings clearly handle), so the exclusion side is only implied by 'may not cover'.

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