Skip to main content
Glama

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

Срок: календар за година

srok_year
Read-onlyIdempotent

Every non-working weekday and every working Saturday in a year in Bulgaria (2020–2099), with the legal basis.

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>"
    },
    "name": "srok_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Output Schema

NameRequiredDescriptionDefault
daysYes
yearYes
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.
decisionsCheckedYes

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.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the description's job is to add substance, which it does: Bulgarian jurisdiction, the 2020–2099 validity window, the inclusion of the legal basis, and the country-specific nuance of 'working Saturdays' (compensatory working days). It does not add caveats about data freshness or gaps for future years, but the core behavior is well disclosed.

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 dense sentence with zero filler, leading with the scope and closing with the legal-basis detail. Nothing could be removed without losing information.

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?

With annotations supplying the safety profile and an output schema covering return structure, the description needs only to pin down jurisdiction, range and content, which it does. A brief note on what 'working Saturday' means or on the granularity of the returned entries would make it fully self-sufficient.

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 0%, so the description must carry the meaning of the single 'year' parameter. It partially does by restating the 2020–2099 range and tying the parameter to a year-long calendar, but it adds no interpretation beyond the schema's own min/max bounds.

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 concrete resource and scope: every non-working weekday plus every working Saturday for a Bulgarian year, with the legal basis. The year-scoped aggregate nature is clear enough to separate it from a single-date sibling like srok_day, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative such as srok_day or srok_deadline. The agent must infer that this is the bulk year view rather than the single-date lookup purely from the phrase 'in a year'.

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