clickedu-mcp

get_calendar

Fetch Clickedu calendar events for a chosen week or month by date, including event times, titles, and owners. Use it to review your teaching schedule or plan ahead.

Instructions

Your Clickedu calendar events, each with date (YYYY-MM-DD), time, title, owner and event_id. view is "week" (default) or "month"; date (YYYY-MM-DD) picks the week/month to show, default today.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_calendar"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`view`	No		week

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the default view and date, which are useful behavioral facts. However, it says nothing about range limits, pagination, whether future/past events are included, or permissions, and the enumerated return fields largely duplicate the output schema.

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

Conciseness4/5

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

Two compact sentences with no filler; the returned shape comes first and parameter behavior second. Formatting is slightly awkward with the unbalanced quotes, but content is front-loaded and efficient.

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?

For a two-optional-parameter read tool with an output schema, the description covers the essentials: what is returned, the date format, and both defaults. The only real gap is its relationship to the semantically similar get_schedule sibling.

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% and the schema gives only bare titles and defaults, so the description must compensate. It does so well: it gives the date format (YYYY-MM-DD), the meaning of 'picks the week/month to show', the 'week'/'month' values for view, and the 'today' default for date.

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

Purpose4/5

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

States a specific verb+resource: retrieving Clickedu calendar events, with the returned fields enumerated. It does not distinguish itself from the sibling get_schedule, which plausibly overlaps, so an agent cannot tell the two apart from the description alone.

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

Usage Guidelines3/5

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

Usage is only implied by the defaults ('week' view, today's date), and there is no statement of when to prefer this over get_schedule or get_student_daily, nor any exclusions.

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