Skip to main content
Glama

get_teacher_roles

Read-onlyIdempotent

Retrieve all teacher roles with pagination support. Use cursor and per_page parameters to control the result set.

Instructions

Get all teacher roles

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 that executes the 'get_teacher_roles' tool logic: calls apiList to GET /teacher_roles with cursor/per_page, logs the response, formats the list result, and appends a next-page cursor if present.
    async ({ cursor, per_page }) => {
      try {
        const result = await apiList<EduframeRecord>("/teacher_roles", { cursor, per_page });
        void logResponse("get_teacher_roles", { cursor, per_page }, result);
        const toolResult = formatList(result.records, "teacher roles");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for 'get_teacher_roles' using Zod: optional 'cursor' (string) and 'per_page' (positive integer).
    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)"),
    },
  • Tool registration call using server.registerTool('get_teacher_roles', ...) inside registerTeacherRoleTools, with description, annotations (readOnlyHint=true), and the handler.
    export function registerTeacherRoleTools(server: McpServer): void {
      server.registerTool(
        "get_teacher_roles",
        {
          description: "Get all teacher roles",
          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>("/teacher_roles", { cursor, per_page });
            void logResponse("get_teacher_roles", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "teacher roles");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • Import of registerTeacherRoleTools from './teacher_roles'.
    import { registerTeacherRoleTools } from "./teacher_roles";
  • registerTeacherRoleTools added to the tools array, which is iterated by registerAllTools.
    registerTeacherRoleTools,
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no further behavioral context such as pagination behavior or response format.

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 efficient sentence with no fluff. It is appropriately concise for a simple tool.

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?

The description omits that results are paginated (implied by cursor and per_page parameters), which is critical for invocation. Without an output schema, this gap reduces completeness.

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 coverage is 100% with both parameters documented. The description does not add additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 'Get all teacher roles' clearly states the verb and resource, distinguishing it from the sibling 'get_teacher_role' (singular). However, it does not specify whether 'all' means the entire collection or with filters, but the context implies a listing operation.

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_teacher_role'. There is no mention of prerequisites, recommended filters, 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