Get upcoming due dates for submissions, questionnaires, exams, and semester events. The default view shows today through the next 30 days, with optional date ranges for custom searches.
Blížící se deadliny: odevzdávárny, odpovědníky, zkoušky a události semestru. Výchozí rozsah: dnes až +30 dní.
| Name | Required | Description | Default |
|---|---|---|---|
| do | No | ||
| od | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It adds the useful default window of today to +30 days and defines the scope, but it does not state whether the operation is read-only, how the od/do parameters interact with the default range, or what happens when parameters are omitted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler, front-loading the core scope and then the default range. It is appropriately sized for a simple listing tool, though a little more parameter guidance would improve it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is complete enough to understand the tool's basic purpose and default behavior, especially since an output schema exists to describe return values. However, the absence of param semantics and explicit sibling differentiation leaves noticeable gaps for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has two undocumented parameters with 0% coverage, and the description only mentions the default range. This indirectly hints that od and do relate to a custom date range, but it does not explain their format, optionality, or interaction with the default, leaving the agent with insufficient guidance for non-default calls.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as upcoming deadlines spanning submission boxes, questionnaires, exams, and semester events, and states a default time range. It is distinguishable from sibling tools like zkouskove_terminy or udalosti by its combined scope, though it lacks an explicit verb such as 'list' or 'show'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is used when a user needs upcoming deadlines, and it communicates the default range. However, it does not mention alternatives or conditions for choosing between this and closely related siblings such as kalendar, rozvrh, or zkouskove_terminy, leaving differentiation to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.