Edupage MCP Server

Overview Schema Source Related Servers Discussions Admin

get_students

Retrieve a list of students in your class from Edupage. Returns a JSON array of student records, with optional filtering by school subdomain.

Instructions

Get students in your class.

Args: school: School subdomain (only needed with multiple schools).

Returns: JSON array of lean student records

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

Input Schema

Name	Required	Description	Default
`school`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Returns JSON array of lean student records and explains the school parameter's condition. No annotations provided, so description carries burden; minimal but adequate disclosure of behavior.

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?

Very concise with two sentences, front-loaded purpose. Could be slightly more structured (e.g., bullet points) but efficient.

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

Completeness3/5

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

For a simple 1-parameter tool with output schema, the description is adequate but lacks details like ordering, pagination, or explanation of 'lean' records. Siblings are numerous but not addressed.

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 coverage is 0% but description adds meaning for the only parameter: 'School subdomain (only needed with multiple schools).' This is valuable beyond the schema's default value.

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?

Clearly states 'Get students in your class' with a specific verb and scope. However, sibling 'get_all_students' exists and there is no differentiation, slightly reducing clarity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'get_all_students' or other teacher-specific tools. Does not mention prerequisites or context.

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