Skip to main content
Glama

Romania Salary Calculator

Romania: what these calculators cover

tax_rules_covered
Read-onlyIdempotent

The Romania rules the calculators apply (2026), the options they take, what is not modelled, and the official sources. 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.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, deterministic, closed-world lookup, so the description does not need to restate safety. It adds useful behavioral context: the reference is scoped to 2026, includes calculator options and non-modelled cases, and points to official sources. It does not describe the output shape, but that is minor for a no-output-schema reference tool.

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 definition is compact and front-loads the coverage scope before the usage instruction. Every clause contributes information, with no filler or repetition.

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 no-parameter, read-only reference tool with annotations and no output schema, the description supplies the essential scope and a call trigger. An agent can decide to call it, though slightly more specificity about the form of the returned reference material would help.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain any inputs, and the empty schema is consistent with a no-argument reference call.

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 resource: the Romanian tax rules the calculators apply for 2026. It also enumerates what the reference covers (options, unmodelled areas, official sources), which distinguishes it from the calculation siblings, though it lacks an explicit verb such as 'describe' or 'list'.

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 routes uncertain coverage questions here. It does not specify which sibling to use for covered questions or give further exclusions, so it is clear but not fully prescriptive.

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