Skip to main content
Glama
Sign In

skanfirmy.pl

by io.github.bartosz-kuc
OverviewDiscussionsAdmin

oblicz_odsetki

Read-onlyIdempotent

Calculate statutory or commercial (B2B) late-payment interest, broken down by NBP reference-rate periods.

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": {
      "kwota": "<kwota>",
      "dataOd": "<dataOd>",
      "dataDo": "<dataDo>",
      "typ": "<typ>"
    },
    "name": "oblicz_odsetki"
  }
}

Input Schema

NameRequiredDescriptionDefault
typYeskc = statutory late-payment interest (Civil Code art. 481, NBP reference rate + 5.5 pp); h10 = commercial B2B transactions, non-public debtor (NBP reference rate on 1 Jan / 1 Jul + 10 pp); h8 = commercial transactions, public healthcare debtor (NBP reference rate on 1 Jan / 1 Jul + 8 pp).
kwotaYesOverdue amount in PLN.
dataDoYesActual payment date, format YYYY-MM-DD.
dataOdYesPayment due date, format YYYY-MM-DD.

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 this is a read-only, idempotent, non-destructive, closed-world operation, so safety behavior is covered. The description adds one genuinely useful behavioral detail — the result is broken into NBP reference-rate sub-periods — but it says nothing about rounding conventions, day-count rules, or what the returned figures look like, which matter for a computation 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?

A single front-loaded sentence with no filler; the computational scope and the per-period breakdown are both stated immediately.

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 must carry the return-value burden, and it only gestures at the output ('broken down by NBP reference-rate periods') without stating whether a total interest figure, per-period subtotals, day counts, or a currency/rounding convention are returned. Combined with the absent guidance on which 'typ' applies, this leaves gaps for a calculation tool, though the 100%-documented schema and full annotations keep it viable.

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%: the 'typ' enum spells out the legal basis and rate markup for kc/h10/h8, and the date/amount parameters are documented with format and currency. The description adds no parameter-level meaning beyond this, so the baseline of 3 is appropriate.

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 names a specific verb and resource ('Calculate statutory or commercial (B2B) late-payment interest') and adds the mode of computation ('broken down by NBP reference-rate periods'). No sibling tool performs interest calculation, so the scope is unambiguous against the surrounding lookup/registration tools.

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 phrase 'statutory or commercial (B2B)' implies there are distinct regimes to choose among, which is supported by the 'typ' enum, but the description never states when to pick one over another or any prerequisites (e.g. that dates must form a valid overdue period, or that the amount must be in PLN). Usage is only implied.

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

All skanfirmy.pl toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources