Skip to main content
Glama

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

Срок: работен ли е денят

srok_day
Read-onlyIdempotent

Whether a date is a working day in Bulgaria, and if not, why (official holiday, the day after a weekend holiday, a government decision, or a weekend).

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": {
      "date": "<date>"
    },
    "name": "srok_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault
dateYes
kindYes
basisNo
sourceNo
workingYes
reasonBgNo
citationsYesEvery source the result rests on. Cite url; give checkedOn or publishedOn.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the classification taxonomy used when the answer is negative, which tells the agent what kind of explanatory detail to expect. It does not add anything about edge cases such as multi-day holiday bridges beyond the one category mentioned.

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?

One sentence, front-loaded with the core question and followed by the parenthetical enumeration of reasons. No filler, no repetition of the tool name or title.

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 single-date, read-only lookup with an output schema and full annotation coverage, the description supplies enough to select and invoke the tool correctly. The only minor gap is the absence of any routing hint to neighboring srok_* tools.

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?

There is a single required parameter whose schema description already states the 'YYYY-MM-DD' format, giving 100% schema coverage. The description adds no format, range, or constraint detail beyond the schema, so the baseline of 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 resource and predicate: whether a given date is a working day in Bulgaria. It also enumerates the non-working categories (official holiday, post-weekend-holiday day, government decision, weekend), which makes the scope unambiguous. It does not explicitly distinguish itself from siblings such as srok_deadline or srok_year, so it stops short of a 5.

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 — an agent can infer it should call this when it needs to know if a single date is a working day. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives like srok_deadline for date arithmetic or srok_year for bulk year data.

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