Skip to main content
Glama

create_planning_attendee

Assign a teacher to a meeting or planning event. Provide the teacher ID, event ID, event type (Meeting or Planning::Event), and optionally a role ID.

Instructions

Assign a teacher to a meeting or planning event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teacher_idYesUnique identifier of the teacher.
attendable_idYesUnique identifier of the attendable.
attendable_typeYesType of the attendable (e.g., "Meeting" or "Planning::Event").
teacher_role_idNoUnique identifier of the teacher role.

Implementation Reference

  • The async handler that executes the create_planning_attendee tool logic: calls apiPost to POST to /planning/attendees, logs the response, and returns a formatted success message.
    async (body) => {
      try {
        const record = await apiPost<EduframeRecord>("/planning/attendees", body);
        void logResponse("create_planning_attendee", body, record);
        return formatCreate(record, "planning attendee");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for create_planning_attendee: requires teacher_id (number), attendable_id (number), attendable_type (enum 'Meeting' | 'Planning::Event'), and optional teacher_role_id (number).
    {
      description: "Assign a teacher to a meeting or planning event.",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
      inputSchema: {
        teacher_id: z.number().int().describe("Unique identifier of the teacher."),
        attendable_id: z.number().int().describe("Unique identifier of the attendable."),
        attendable_type: planningAttendeeAttendableTypeEnum.describe(
          'Type of the attendable (e.g., "Meeting" or "Planning::Event").',
        ),
        teacher_role_id: z.number().int().optional().describe("Unique identifier of the teacher role."),
      },
    },
  • Registration of create_planning_attendee via server.registerTool within the registerPlanningAttendeeTools function.
    export function registerPlanningAttendeeTools(server: McpServer): void {
      server.registerTool(
        "create_planning_attendee",
        {
          description: "Assign a teacher to a meeting or planning event.",
          annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
          inputSchema: {
            teacher_id: z.number().int().describe("Unique identifier of the teacher."),
            attendable_id: z.number().int().describe("Unique identifier of the attendable."),
            attendable_type: planningAttendeeAttendableTypeEnum.describe(
              'Type of the attendable (e.g., "Meeting" or "Planning::Event").',
            ),
            teacher_role_id: z.number().int().optional().describe("Unique identifier of the teacher role."),
          },
        },
        async (body) => {
          try {
            const record = await apiPost<EduframeRecord>("/planning/attendees", body);
            void logResponse("create_planning_attendee", body, record);
            return formatCreate(record, "planning attendee");
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • Import and registration of registerPlanningAttendeeTools in the main tools index, which wires it into the MCP server.
    import { registerPlanningAttendeeTools } from "./planning_attendees";
    import { registerPlanningConflictTools } from "./planning_conflicts";
    import { registerPlanningEventTools } from "./planning_events";
    import { registerPlanningLocationTools } from "./planning_locations";
    import { registerPlanningMaterialTools } from "./planning_materials";
    import { registerPlanningRequiredTeacherGroupAttendeeTools } from "./planning_required_teacher_group_attendees";
    import { registerPlanningTeacherTools } from "./planning_teachers";
    import { registerProgramEditionTools } from "./program_editions";
    import { registerProgramElementTools } from "./program_elements";
    import { registerProgramEnrollmentTools } from "./program_enrollments";
    import { registerProgramPersonalProgramElementTools } from "./program_personal_program_elements";
    import { registerProgramProgramTools } from "./program_programs";
    import { registerReferralTools } from "./referrals";
    import { registerSignupQuestionTools } from "./signup_questions";
    import { registerTaskTools } from "./tasks";
    import { registerTeacherEnrollmentTools } from "./teacher_enrollments";
    import { registerTeacherRoleTools } from "./teacher_roles";
    import { registerTeacherTools } from "./teachers";
    import { registerTheseTools } from "./theses";
    import { registerUserTools } from "./users";
    import { registerWebhookNotificationTools } from "./webhook_notifications";
    import { registerWebhookTools } from "./webhooks";
    
    const tools: Array<(server: McpServer) => void> = [
      registerAccountTools,
      registerAffiliationTools,
      registerAttendanceTools,
      registerAuthenticationTools,
      registerCatalogProductTools,
      registerCatalogVariantTools,
      registerCategorieTools,
      registerCertificateTools,
      registerCommentTools,
      registerCourseLocationTools,
      registerCourseTabTools,
      registerCourseVariantTools,
      registerCourseTools,
      registerCreditCategorieTools,
      registerCreditTools,
      registerCustomAssociationTools,
      registerCustomFieldOptionTools,
      registerCustomObjectTools,
      registerCustomRecordTools,
      registerDiscountCodeTools,
      registerEditionDescriptionSectionTools,
      registerEducatorTools,
      registerEmailTools,
      registerEnrollmentTools,
      registerGradeTools,
      registerInvoiceVatTools,
      registerInvoiceTools,
      registerLabelTools,
      registerLeadTools,
      registerMaterialGroupTools,
      registerMaterialTools,
      registerMeetingLocationTools,
      registerMeetingTools,
      registerOrderTools,
      registerOrganizationTools,
      registerPaymentMethodTools,
      registerPaymentOptionTools,
      registerPaymentTools,
      registerPlannedCourseTools,
      registerPlanningAttendeeTools,
      registerPlanningConflictTools,
      registerPlanningEventTools,
      registerPlanningLocationTools,
      registerPlanningMaterialTools,
      registerPlanningRequiredTeacherGroupAttendeeTools,
      registerPlanningTeacherTools,
      registerProgramEditionTools,
      registerProgramElementTools,
      registerProgramEnrollmentTools,
      registerProgramPersonalProgramElementTools,
      registerProgramProgramTools,
      registerReferralTools,
      registerSignupQuestionTools,
      registerTaskTools,
      registerTeacherEnrollmentTools,
      registerTeacherRoleTools,
      registerTeacherTools,
      registerTheseTools,
      registerUserTools,
      registerWebhookNotificationTools,
      registerWebhookTools,
    ];
Behavior3/5

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

Annotations indicate it's not read-only, not destructive, and not idempotent, aligning with a create operation. Description adds no further behavioral context (e.g., permissions, side effects).

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?

Single, concise sentence with no unnecessary words. Front-loaded with essential information.

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?

The description, combined with schema, is minimally adequate for a standard create operation. Lacks explanation of return values or workflow context.

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?

Input schema provides 100% coverage with descriptions for all parameters. Description does not add additional semantics beyond the schema.

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 a teacher') and the target ('meeting or planning event'). It distinguishes from siblings like 'create_planning_required_teacher_group_attendee' by not specifying group, but does not explicitly contrast.

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 such as 'create_planning_required_teacher_group_attendee'. No context about prerequisites 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