Fetch upcoming UNED campus calendar events—assignments, exams, and tutoring sessions—within a chosen number of days to track deadlines and plan study.
Eventos del calendario (entregas, exámenes, tutorías…) de los próximos N días.
| Name | Required | Description | Default |
|---|---|---|---|
| dias | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does disclose one behavioral fact — results are forward-looking, limited to the next N days — but says nothing about read-only nature, authentication requirements, timezone/date handling, or whether past or canceled events appear.
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?
One sentence, front-loaded with the resource and the constraint, and the parenthetical examples add disambiguation without bloat. Nothing is wasted.
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?
An output schema exists, so return values need not be explained, and the tool is simple (one optional parameter). Still, the description omits the parameter default and gives no sibling routing, which matters in a 21-tool namespace where it overlaps uned_entregas and uned_clases.
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?
Schema description coverage is 0%, so the description must compensate for the single 'dias' parameter. 'Próximos N días' does map the parameter to a window length, but it omits the default of 30 days and any bounds or format constraints.
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?
Names a specific resource (eventos del calendario) and scope (próximos N días), with parenthetical examples (entregas, exámenes, tutorías) that make the content concrete. However, it does not differentiate itself from closely overlapping siblings such as uned_entregas, uned_clases, or uned_calendario_ics, so an agent must infer which one to pick.
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 only states what the tool returns; it never says when to use this versus uned_calendario_ics, uned_entregas, uned_clases, or uned_plan. With 21 sibling tools in the namespace, the absence of any routing guidance is a real gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.