Skip to main content
Glama

Czy Stacja Neapol jest otwarta

is_open_on
Read-onlyIdempotent

Użyj, gdy ktoś pyta, czy Stacja Neapol jest otwarta dziś, w konkretny dzień, w święto albo o danej godzinie. Uwzględnia dni specjalne z kalendarza restauracji. Use when someone asks whether Stacja Neapol is open today, on a date, on a holiday or at a given time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "is_open_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoData w formacie YYYY-MM-DD (strefa Europe/Warsaw). Brak = dzisiaj. / Date as YYYY-MM-DD; defaults to today.
timeNoGodzina HH:MM. / Time as HH:MM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real behavioral context the annotations don't: 'Uwzględnia dni specjalne z kalendarza restauracji' tells the agent that special calendar days are factored in, so holiday results are trustworthy without extra flags. It doesn't describe the shape of the answer (e.g. open/closed plus hours), which is the remaining gap.

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 trigger and with the special-days caveat in a clear second position. The Polish/English duplication doubles length without adding information, but it is a deliberate bilingual pattern rather than padding.

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 simple two-parameter, zero-required read tool with no output schema and full annotation coverage, the definition supplies what an agent needs to decide to call it and how to phrase the arguments. The one omission is that with no output schema present, nothing states what the result looks like beyond an implicit open/closed answer.

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 coverage is 100% and the schema already documents both parameters in two languages, including the YYYY-MM-DD format, the Europe/Warsaw timezone and the 'brak = dzisiaj' default. The description's only added meaning is that holidays are resolved internally, implying no separate holiday flag is needed. Baseline 3 applies since the schema carries the parameter burden.

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 names a concrete verb+resource: answering whether 'Stacja Neapol jest otwarta' for today, a specific date, a holiday, or a given hour. That is specific enough to separate it from siblings like get_there_by_train or whats_made_here. It stops short of 5 because it never explicitly contrasts itself with plan_visit, which could plausibly also surface opening-hour information.

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

Usage Guidelines4/5

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

Explicit trigger conditions are given: 'dziś, w konkretny dzień, w święto albo o danej godzinie' / 'today, on a date, on a holiday or at a given time'. That covers the main query shapes an agent would route here. There is no when-not guidance or named alternative for adjacent questions such as planning a full visit.

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