Skip to main content
Glama
tresor4k

macalc

calculate_uk_ni_contributions

Compute UK National Insurance (Class 1 employee) contributions for 2025/26. Input annual salary in GBP to receive annual and monthly NI amounts along with effective tax rate.

Instructions

Calculate UK National Insurance contributions (Class 1 employee) for 2025/26. Returns: {annual_salary, ni_annual, ni_monthly, effective_rate_pct}. See list_bundles for related 'finance-uk' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annual_salaryYesAnnual gross salary in GBP

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It accurately states the tool calculates Class 1 employee NI contributions for a specific tax year, which is sufficient. However, it could add context about rate based on 2025/26 thresholds.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: one explains purpose and return fields, the other references related calculators. It is front-loaded and concise with no extra words.

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

Completeness5/5

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

Given low complexity (one parameter), no annotations, and an output schema, the description adequately covers purpose, input, and output. It mentions return fields and directs to a bundle for related calculators.

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 single parameter 'annual_salary' is described in the schema as 'Annual gross salary in GBP' (100% coverage). The description adds the tax year '2025/26', which provides additional context beyond the schema.

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 UK National Insurance contributions for Class 1 employee in 2025/26, with a specific verb and resource. It distinguishes itself from siblings like 'calculate_uk_income_tax' by specifying NI contributions.

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?

The description references 'list_bundles' for related 'finance-uk' calculators, providing some context, but lacks explicit when-to-use or when-not-to-use guidance and does not mention alternatives for other NI classes or employer contributions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server