clickedu-mcp

get_class_behaviour

Retrieves a class group's behaviour records—incidents and merits—for a specified date range, returning an empty status when nothing is recorded and never modifying data.

Instructions

Behaviour record ('Comportament': incidències and mèrits) of one class group for a date range, as Clickedu's reports. status "empty" means the page was read and there is nothing recorded in that range. Read-only: it never creates or changes an incident or sanction.

class_id from get_subjects_and_rosters; dates YYYY-MM-DD, default the current school year. For one student's day-by-day items (behaviour notes included) use get_student_daily.

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": {
      "class_id": "<class_id>"
    },
    "name": "get_class_behaviour"
  }
}

Input Schema

Name	Required	Description	Default
`date_to`	No
`class_id`	Yes
`date_from`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does address the key trait: 'Read-only: it never creates or changes an incident or sanction.' It also pre-explains the 'empty' status so the agent does not misread an empty result as a failure. It stops short of covering auth, pagination, or volume limits for a full-year class query.

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

Conciseness3/5

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

Content is front-loaded with the purpose first and the sibling redirect last, which is the right order. However, the prose is choppy and line-broken mid-sentence ('One class / group', 'status "empty" means'), and the parenthetical gloss plus 'as Clickedu's reports' add slight clutter without much payoff.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, prerequisites, parameter formats, read-only safety, and the sibling alternative. What remains thin is the range/edge behavior of the date parameters and what the non-'empty' statuses are.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does for all three parameters: it names the source of class_id and specifies the YYYY-MM-DD format and current-school-year default for both date bounds. Minor gap: it does not say whether the range is inclusive or how date_from/date_to interact if only one is supplied.

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 specific verb and resource ('Behaviour record of one class group for a date range') and immediately clarifies the domain term with the Catalan original ('Comportament': incidències and mèrits). It explicitly distinguishes itself from the nearest sibling by naming get_student_daily as the per-student alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this for a whole class group, use get_student_daily for one student's day-by-day items. It also names the prerequisite source for class_id (get_subjects_and_rosters) and the default behavior for omitted dates, leaving nothing to inference.

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