clickedu-mcp

get_schedule

Retrieves a teacher's weekly teaching timetable, including each class session's day, time, subject, group, room, co-teachers, and session-detail link.

Instructions

Your weekly teaching timetable: each class session with day, time, subject, group, room, co-teachers, and a link to the session detail.

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_schedule"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does describe the returned fields well. However, it never states scope behavior such as whether it always returns the current week or which week it covers, nor does it confirm this is read-only. That leaves a meaningful gap for a no-parameter tool whose behavior is entirely determined by implicit context.

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?

A single sentence with the resource stated first and the returned fields enumerated afterward, with no filler. The colon-and-list structure makes it easy to scan. Slightly dense but every clause contributes information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and with zero parameters there is no argument surface to cover. For a simple read-only fetch tool, stating the resource and its contents is sufficient for correct invocation. The only omission, week scope, is minor given the fixed no-argument signature.

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?

The tool takes zero parameters, so there is nothing for the schema to document and the description does not need to explain argument meaning. Baseline 4 applies; no parameter information is missing or misleading.

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?

The description names a specific resource and scope: the weekly teaching timetable, listing the concrete fields each session carries (day, time, subject, group, room, co-teachers). It even differentiates itself from get_session_detail by noting each entry links to the session detail. It stops short of 5 only because the verb is implicit rather than stated.

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?

There is no explicit when-to-use or when-not-to-use statement, but the mention of 'a link to the session detail' hints that get_session_detail is the follow-up for deeper per-session information. An agent can infer this is the entry point for a weekly overview, but the routing is left to inference rather than spelled out.

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