clickedu-mcp

get_attendance

Read the current attendance for one session: each student's present, absent, or late status, reason, and justified flag. Use cgap and sessio from a session detail link.

Instructions

Read the CURRENT attendance state for one session: each student with their status (present / absent / late), reason, and justified flag. cgap and sessio come from the attendance_link in get_session_detail (assistencia/index.php?cgap=...&sessio=...&n=...). Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cgap": "<cgap>",
      "sessio": "<sessio>"
    },
    "name": "get_attendance"
  }
}

Input Schema

Name	Required	Description	Default
`n`	No
`cgap`	Yes
`sessio`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key trait ('Read-only') plus the exact fields returned per student ('status ... reason, justified flag'). It leaves undescribed whether prior/historical attendance is retrievable and what the opaque cgap/sessio identifiers actually represent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the outcome, then the parameter provenance, then a one-word safety tag. The URL template is compact and earns its place by clarifying the identifier format rather than restating the schema.

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?

Return values are already covered by an output schema but the description reinforces them anyway, and the prerequisite call chain is spelled out. The only shortfall for a 3-param read tool is the undocumented 'n' parameter.

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 description coverage is 0%, so the description must compensate. It successfully explains where cgap and sessio originate (attendance_link in get_session_detail) and reinforces correct format via the URL template, but the third parameter 'n' (integer, default 0) is never mentioned, leaving a real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource ('Read the CURRENT attendance state for one session') and enumerates the payload (status, reason, justified flag). The 'CURRENT' and 'one session' qualifiers implicitly separate it from get_monthly_attendance (aggregate) and from mark_attendance (write), so an agent can route without opening the schema.

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?

Explicitly routes the agent through a prerequisite: cgap and sessio must come from the attendance_link in get_session_detail, with the URL pattern shown. That is strong when/how-to-use guidance, but there is no explicit exclusion telling the agent when to prefer get_monthly_attendance or get_class_behaviour instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.