Skip to main content
Glama

Нишка – отворен слой

Срок: последен ден

srok_deadline
Read-onlyIdempotent

Count a Bulgarian legal deadline the way the Civil Procedure Code does (ГПК чл. 60): days count from the day after the event; weeks, months and years end on the corresponding date; an end on a non-working day moves to the next working day. Returns the last day and each step with its reason. Other laws can have their own rules: tell the user to check the letter or the law.

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": {
      "from": "<from>",
      "amount": "<amount>",
      "unit": "<unit>"
    },
    "name": "srok_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe day of the event the deadline runs from, YYYY-MM-DD (e.g. the day a letter was received).
unitYes
amountYes

Output Schema

NameRequiredDescriptionDefault
endYesThe last day to act, YYYY-MM-DD.
fromYes
ruleYes
unitYes
amountYes
stepsBgYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
movedOverNo
countedEndNoWhere the count lands before the non-working-day rule.
calendarCheckedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / citations / items / properties / licence / enum
      Previous value: -[
      -  "CC-BY-4.0",
      -  "official-record"
      -]New value: +[
      +  "CC-BY-4.0",
      +  "official-record",
      +  "ODbL-1.0"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious behavior: the counting algorithm (day after the event, corresponding-date endings, rollover from a non-working day) and the return shape ('the last day and each step with its reason'). It does not address how the 'working_days' unit interacts with the calendar-day CPC rule, which is the one behavioral ambiguity left.

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 sentences, front-loaded with the governing rule, then the algorithm, then the return shape, then the caveat. Every clause carries information. The final caveat is slightly advisory but justified for a legal-calculation tool.

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?

An output schema exists and the description needn't enumerate return values; annotations cover the safety profile. For a 3-parameter computational tool the description is close to complete. The remaining hole is the semantics of the 'working_days' unit relative to the stated calendar-day rule.

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 only 33% ('amount' and the enum values carry no prose), so the description must compensate. It does clarify how the 'from' date is interpreted (the event day, then counting starts the next day), which is meaningful beyond the schema. It says nothing about 'amount' bounds or how the 'working_days' enum value behaves, leaving a real gap.

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?

States a specific verb and resource ('count a Bulgarian legal deadline'), names the governing rule (ГПК чл. 60), and describes the output shape. It is not tautological with the title. It does not explicitly contrast itself with the sibling calculators (srok_day, srok_year, document_deadline), so differentiation is left implicit.

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 scope is implied by 'the way the Civil Procedure Code does' plus the closing caveat that other laws can have their own rules and the user should check the letter or the law. That is a useful when-not hint, but there is no explicit instruction on when to pick this over the other srok_*/document_deadline tools, which is exactly the ambiguity an agent faces here.

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