guarani_estado_cursadaRetrieve active course enrollments, schedules, regular status, and accumulated absences from SIU Guaraní, optionally filtered by degree name or code.
Detalla cursadas activas, horarios, regularidad e inasistencias acumuladas en SIU Guaraní.
| Name | Required | Description | Default |
|---|---|---|---|
| carrera | No | Nombre o código de la carrera (opcional) |
Changes observed during successful MCP inspections.
v1.0.8Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesRemoved value: -falseOutput schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "cursadas": {
- "type": "array"
- },
- "total": {
- "type": "number"
- }
- },
- "required": [
- "cursadas"
- ],
- "type": "object"
-}New value: +nullv1.0.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral content by disclosing exactly which data is returned (regularidad, inasistencias acumuladas). It does not say whose cursadas are reported (authenticated student only?) or how the optional career filter affects the result set.
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?
A single, front-loaded sentence that lists the returned data points with zero filler. 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.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description is the only source of return-value information, and it does list the reported fields, which is a plus. However, for an openWorld tool with an optional filter parameter, it omits scope (per-student vs. filtered by career) and any note on data freshness or how absences are counted. Adequate but with clear gaps.
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 100% and there is only one optional parameter ('carrera'), so the schema already carries the semantics. The description never references the parameter or explains whether it narrows the output to one career. Baseline 3 is appropriate since the schema does the work.
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 names a specific verb ('Detalla') and a concrete set of resources: active courses, schedules, regularity status and accumulated absences in SIU Guaraní. An agent can tell this is about current enrollment status, not historical records or exam tables. It stops short of naming how it differs from close siblings like guarani_horario_semanal or guarani_historia_academica.
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?
There is no guidance on when to invoke this tool versus alternatives such as guarani_horario_semanal (weekly schedule) or guarani_progreso_carrera, despite heavy overlap in the sibling list. Usage is only inferable from the description's field list. No exclusions, no prerequisites, no mention of whether authentication is required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.