Skip to main content
Glama

get_planning_teachers

Read-onlyIdempotent

Retrieve a paginated list of all available teachers for planning and scheduling purposes.

Instructions

Get all teachers that are available

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for fetching the next page of results
per_pageNoNumber of results per page (default: 25)

Implementation Reference

  • The async handler function for the 'get_planning_teachers' tool. It calls apiList('/planning/teachers', ...), logs the response, formats the result via formatList, and appends a next-cursor hint if pagination is used.
    async ({ cursor, per_page }) => {
      try {
        const result = await apiList<EduframeRecord>("/planning/teachers", { cursor, per_page });
        void logResponse("get_planning_teachers", { cursor, per_page }, result);
        const toolResult = formatList(result.records, "planning teachers");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema definition for 'get_planning_teachers'. Accepts optional 'cursor' (string) and 'per_page' (positive integer). Described as 'Get all teachers that are available' with readOnly/destructive/idempotent annotations.
    {
      description: "Get all teachers that are available",
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
      inputSchema: {
        cursor: z.string().optional().describe("Cursor for fetching the next page of results"),
        per_page: z.number().int().positive().optional().describe("Number of results per page (default: 25)"),
      },
  • Registration function 'registerPlanningTeacherTools' that calls server.registerTool('get_planning_teachers', ...). This is the complete tool registration block.
    export function registerPlanningTeacherTools(server: McpServer): void {
      server.registerTool(
        "get_planning_teachers",
        {
          description: "Get all teachers that are available",
          annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
          inputSchema: {
            cursor: z.string().optional().describe("Cursor for fetching the next page of results"),
            per_page: z.number().int().positive().optional().describe("Number of results per page (default: 25)"),
          },
        },
        async ({ cursor, per_page }) => {
          try {
            const result = await apiList<EduframeRecord>("/planning/teachers", { cursor, per_page });
            void logResponse("get_planning_teachers", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "planning teachers");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
    }
  • Import of 'registerPlanningTeacherTools' from './planning_teachers' in the central tools index.
    import { registerPlanningTeacherTools } from "./planning_teachers";
  • The 'registerPlanningTeacherTools' is included in the tools array, which is iterated by 'registerAllTools' to register all tools on the server.
    registerPlanningTeacherTools,
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. The description adds no extra behavioral details such as pagination or what 'available' means in terms of state.

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?

The description is a single short sentence, which is concise. However, it could be more informative without becoming lengthy, as it omits important context.

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

Completeness2/5

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

Given the simple tool with two optional parameters and no output schema, the description is incomplete. It fails to clarify the meaning of 'available' in a planning context or how this tool relates to other planning tools. The minimal annotations cover safety but not usage nuance.

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 100%, with both parameters clearly described in the schema. The description adds no additional meaning beyond what is already in the input schema.

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

Purpose3/5

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

The description states 'get all teachers that are available,' which identifies a verb and resource. However, 'available' is vague and does not differentiate from the sibling tool 'get_teachers' which likely returns all teachers without filtering.

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 is provided on when to use this tool versus alternatives like 'get_teachers' or other planning tools. The description does not specify any context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martijnpieters/eduframe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server