List recorded sessions for a course from the attendance tool to review logged meetings; these entries do not equal the full academic timetable or proof of attendance.
Sesiones registradas en la herramienta de asistencia del curso. No equivale al horario académico completo ni confirma presencia.
| Name | Required | Description | Default |
|---|---|---|---|
| courseId | Yes |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds an important semantic caveat beyond annotations: these are attendance-tool sessions, not the full academic schedule, and they do not confirm presence. It still omits pagination, auth, or return-shape details.
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?
Two short sentences, both earning their place: the first defines the resource, and the second immediately states the key limitation. It is appropriately sized and front-loaded.
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 tool is simple and annotations cover safety behavior, while the description usefully clarifies data scope. However, the required courseId remains undocumented in both schema and description, leaving an agent without enough information about the parameter to invoke the tool confidently.
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?
There is one required parameter, courseId, and schema description coverage is 0%. The description never mentions courseId, its meaning, or the expected ^_\d+_\d+$ format, so it does not compensate for the missing schema documentation.
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?
States the resource clearly: sessions recorded in the course attendance tool. It also distinguishes the scope from the full academic schedule and from presence confirmation, but it lacks an explicit action verb such as 'list' or 'retrieve'.
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 says what the tool is not, which helps avoid confusion with schedule or attendance-confirmation data. However, it does not say when to use this tool versus alternatives such as blackboard_get_my_attendance, calendar tools, or agenda tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.