Skip to main content
Glama
martijnpieters

eduframe-mcp

by martijnpieters
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

create_planning_required_teacher_group_attendee

Assign a teacher to a required teacher group to satisfy planning requirements.

Instructions

Assign a teacher to a required teacher group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teacher_idYesUnique identifier of the teacher to assign.
required_teacher_group_idYesUnique identifier of the required teacher group to satisfy.

Implementation Reference

  • src/tools/planning_required_teacher_group_attendees.ts:21-30 (handler)
    The async handler that executes the tool logic - calls apiPost to create a planning required teacher group attendee and formats the result.
      async (body) => {
    try {
      const record = await apiPost<EduframeRecord>("/planning/required_teacher_group_attendees", body);
      void logResponse("create_planning_required_teacher_group_attendee", body, record);
      return formatCreate(record, "planning required teacher group attendee");
    } catch (error) {
      return formatError(error);
    }
  },
);
  • src/tools/planning_required_teacher_group_attendees.ts:10-20 (schema)
    Input schema definition for the tool, requiring teacher_id and required_teacher_group_id as integer properties.
    {
  description: "Assign a teacher to a required teacher group",
  annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
  inputSchema: {
    teacher_id: z.number().int().describe("Unique identifier of the teacher to assign."),
    required_teacher_group_id: z
      .number()
      .int()
      .describe("Unique identifier of the required teacher group to satisfy."),
  },
},
  • src/tools/planning_required_teacher_group_attendees.ts:7-30 (registration)
    The function registerPlanningRequiredTeacherGroupAttendeeTools that registers the tool on the McpServer with name 'create_planning_required_teacher_group_attendee'.
    export function registerPlanningRequiredTeacherGroupAttendeeTools(server: McpServer): void {
  server.registerTool(
    "create_planning_required_teacher_group_attendee",
    {
      description: "Assign a teacher to a required teacher group",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
      inputSchema: {
        teacher_id: z.number().int().describe("Unique identifier of the teacher to assign."),
        required_teacher_group_id: z
          .number()
          .int()
          .describe("Unique identifier of the required teacher group to satisfy."),
      },
    },
    async (body) => {
      try {
        const record = await apiPost<EduframeRecord>("/planning/required_teacher_group_attendees", body);
        void logResponse("create_planning_required_teacher_group_attendee", body, record);
        return formatCreate(record, "planning required teacher group attendee");
      } catch (error) {
        return formatError(error);
      }
    },
  );
  • src/tools/index.ts:109-109 (registration)
    Where the registration function is called in the tools index.
    registerPlanningRequiredTeacherGroupAttendeeTools,

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

The description only says 'Assign' which implies a create/relate operation, but with annotations all false (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds no extra behavioral context. It doesn't disclose what happens on duplicate assignments, side effects, or required permissions.

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

Conciseness5/5

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

The description is a single, concise sentence that communicates the core action with no wasted words. It is front-loaded and 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 assignment tool with two parameters and no output schema, the description covers the basic action but omits return values (e.g., what ID is returned) and any constraints (e.g., uniqueness). It is adequate but not complete.

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?

The input schema has 100% description coverage on both parameters (teacher_id and required_teacher_group_id), so the baseline is 3. The description does not add any additional context about the parameters beyond what the schema provides.

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 clearly states the action ('Assign') and resource ('a teacher to a required teacher group'), making the tool's purpose straightforward. However, it does not distinguish this from sibling tools like create_teacher_enrollment or create_planning_attendee that also involve assigning teachers, so it loses some 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., create_teacher_enrollment) or when not to use it. There is no mention of prerequisites, conditions, or typical scenarios.

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