Skip to main content
Glama

Kalkulator B2B

Dni robocze

working_days
Read-only

Dni i godziny robocze w miesiącu według polskiego kalendarza świąt — do wyceny kontraktu godzinowego. Nie zakłada „22 dni": każdy miesiąc jest policzony.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "working_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesRok podatkowy — decyduje o stałych (progi, ZUS, płaca minimalna)
monthYesMiesiąc 1-12
dailyHoursNoGodzin dziennie

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the safety burden is light. The description adds genuinely useful behavioral context — the Polish holiday calendar and the explicit note that it does not assume a flat "22 days" — but says nothing about the shape of the result (counts vs. day list) or edge cases such as holidays falling on weekends.

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 resource and calendar basis, with the corrective note about not assuming 22 days placed second where it functions as a differentiator. No filler, though the pricing-call-to-action could be folded into the first sentence.

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

Completeness3/5

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

With no output schema, the description should convey what comes back; "days and hours" hints at two totals but leaves unclear whether the result is a scalar pair, a per-day breakdown, or includes holiday names. For a small read-only calculator this is adequate but not complete.

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%, so year, month, and dailyHours are already documented in the schema, including the 2024–2030 range and the 8-hour default. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 verb-and-resource pair: counting working days and hours in a given month under the Polish holiday calendar, and ties it to a concrete use (hourly-contract pricing). It is clear what the tool computes, though it does not explicitly contrast itself with siblings such as tax_deadlines that also deal with calendar data.

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 is only implied through the phrase "do wyceny kontraktu godzinowego" (for hourly contract pricing). There is no statement of when not to use it, no prerequisites, and no named alternative, so the agent must infer the call context.

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