Skip to main content
Glama

Bulgaria Salary and Income Tax Calculator

Employer cost of a salary in Bulgaria

employer_cost
Read-onlyIdempotent

What a salary in Bulgaria costs the employer (employer social contributions itemised), or the reverse: the gross salary a total budget allows. Give gross_annual or budget_annual.

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

Input Schema

NameRequiredDescriptionDefault
childrenNoNumber of dependent children. Default 0.
bonus_annualNoYearly bonus in EUR. Default 0.
child_reliefNoClaim the children relief Default true.
gross_annualNoGross yearly salary in EUR
budget_annualNoTotal yearly employer budget in EUR, to find the gross salary it allows

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the employer social contributions are itemised, the tool works in either direction, and the jurisdiction is Bulgaria. It stops short of describing the response shape or the failure behavior when the two mode inputs are missing or conflicting.

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?

Two sentences, front-loaded with what the tool computes and immediately followed by the one input constraint that matters. Nothing is repeated from the schema or the title, and no sentence is expendable.

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 read-only, non-destructive calculator with full schema documentation and no output schema, this is nearly complete: mode selection, jurisdiction and itemisation are all stated. The only meaningful gap is that no parameter is required, so the description never tells the agent what the tool does when both mode inputs are absent.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds a semantic the schema cannot express: gross_annual and budget_annual are mutually exclusive mode selectors rather than ordinary optional fields. The four relief/bonus/children parameters are left entirely to the schema, which is acceptable given full coverage.

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 states a specific calculation and jurisdiction: employer cost of a Bulgarian salary with itemised social contributions, plus the inverse budget-to-gross direction. That distinguishes it in substance from net_salary and gross_for_target_net, but it never names those siblings, so the agent must infer the boundary itself.

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 closing sentence 'Give gross_annual or budget_annual' tells the agent which input selects which mode, which is real usage guidance. There is no explicit when-to-use-this-vs-alternatives statement, no exclusion, and no statement about what happens if neither or both are supplied.

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