Skip to main content
Glama

create_planned_course

Create a planned course instance by setting its course variant, type, cost, and optional attributes such as dates and participant limits.

Instructions

Create a planned course.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
is_publishedNoBoolean if is published on the website.
course_idYesUnique identifier of the course.
typeYesThe type of the course.
start_dateNoDate at which the planned course starts. Only needed for fixed planned courses.
end_dateNoDate at which the planned course ends. Only needed for fixed planned courses.
min_participantsNoA number representing the minimum number of participants that can enroll for the planned course.
max_participantsNoA number representing the maximum number of participants that can enroll for the planned course.
cost_schemeNoThe cost schema that the payment will follow for the specified course.
costYesThe price to be paid for this planned course. Required if cost_scheme is student (default value) or order.
course_variant_idNoUnique identifier of the course variant.
course_location_idNoUnique identifier of the course location.
durationNoThe period of time of the planned course in days. Only needed for flexible planned courses.
teacher_idsNoThe ids of the teachers in the course
customNo
custom_associationsNo

Implementation Reference

  • The handler function for 'create_planned_course' tool. It receives the body (input params), calls apiPost to POST to '/planned_courses', logs the response, and formats the result as a successful creation.
    async (body) => {
      try {
        const record = await apiPost<EduframeRecord>("/planned_courses", body);
        void logResponse("create_planned_course", body, record);
        return formatCreate(record, "planned course");
      } catch (error) {
        return formatError(error);
      }
    },
  • The input schema for 'create_planned_course' defining all valid parameters: is_published, course_id, type, start_date, end_date, min_participants, max_participants, cost_scheme, cost, course_variant_id, course_location_id, duration, teacher_ids, custom, custom_associations.
    {
      description: "Create a planned course.",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
      inputSchema: {
        is_published: z.boolean().optional().describe("Boolean if is published on the website."),
        course_id: z.number().int().describe("Unique identifier of the course."),
        type: plannedCourseTypeEnum.describe("The type of the course."),
        start_date: z
          .string()
          .optional()
          .describe("Date at which the planned course starts. Only needed for fixed planned courses."),
        end_date: z
          .string()
          .optional()
          .describe("Date at which the planned course ends. Only needed for fixed planned courses."),
        min_participants: z
          .number()
          .int()
          .optional()
          .describe("A number representing the minimum number of participants that can enroll for the planned course."),
        max_participants: z
          .number()
          .int()
          .optional()
          .describe("A number representing the maximum number of participants that can enroll for the planned course."),
        cost_scheme: plannedCourseCostSchemeEnum
          .optional()
          .describe("The cost schema that the payment will follow for the specified course."),
        cost: z
          .number()
          .describe(
            "The price to be paid for this planned course. Required if cost_scheme is student (default value) or order.",
          ),
        course_variant_id: z.number().int().optional().describe("Unique identifier of the course variant."),
        course_location_id: z.number().int().optional().describe("Unique identifier of the course location."),
        duration: z
          .number()
          .optional()
          .describe("The period of time of the planned course in days. Only needed for flexible planned courses."),
        teacher_ids: z.array(z.number().int()).optional().describe("The ids of the teachers in the course"),
        custom: z.record(z.unknown()).optional(),
        custom_associations: z.record(z.unknown()).optional(),
      },
  • Registration of 'create_planned_course' tool via server.registerTool() within registerPlannedCourseTools().
    server.registerTool(
      "create_planned_course",
      {
        description: "Create a planned course.",
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false },
        inputSchema: {
          is_published: z.boolean().optional().describe("Boolean if is published on the website."),
          course_id: z.number().int().describe("Unique identifier of the course."),
          type: plannedCourseTypeEnum.describe("The type of the course."),
          start_date: z
            .string()
            .optional()
            .describe("Date at which the planned course starts. Only needed for fixed planned courses."),
          end_date: z
            .string()
            .optional()
            .describe("Date at which the planned course ends. Only needed for fixed planned courses."),
          min_participants: z
            .number()
            .int()
            .optional()
            .describe("A number representing the minimum number of participants that can enroll for the planned course."),
          max_participants: z
            .number()
            .int()
            .optional()
            .describe("A number representing the maximum number of participants that can enroll for the planned course."),
          cost_scheme: plannedCourseCostSchemeEnum
            .optional()
            .describe("The cost schema that the payment will follow for the specified course."),
          cost: z
            .number()
            .describe(
              "The price to be paid for this planned course. Required if cost_scheme is student (default value) or order.",
            ),
          course_variant_id: z.number().int().optional().describe("Unique identifier of the course variant."),
          course_location_id: z.number().int().optional().describe("Unique identifier of the course location."),
          duration: z
            .number()
            .optional()
            .describe("The period of time of the planned course in days. Only needed for flexible planned courses."),
          teacher_ids: z.array(z.number().int()).optional().describe("The ids of the teachers in the course"),
          custom: z.record(z.unknown()).optional(),
          custom_associations: z.record(z.unknown()).optional(),
        },
      },
      async (body) => {
        try {
          const record = await apiPost<EduframeRecord>("/planned_courses", body);
          void logResponse("create_planned_course", body, record);
          return formatCreate(record, "planned course");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The tool registration function registerPlannedCourseTools is included in the list of all tool registrations, called during server setup.
    registerPlannedCourseTools,
  • The apiPost helper function used by the handler to POST data to the Eduframe API endpoint.
    export async function apiPost<T>(path: string, body: unknown): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "POST",
        headers: buildHeaders(token),
        body: JSON.stringify(body),
      });
    
      return handleResponse<T>(response);
Behavior2/5

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

The description only indicates a create operation. Annotations show readOnlyHint=false and destructiveHint=false, but the description adds no behavioral details such as permissions, side effects, or validation constraints. For a tool with no output schema, more transparency is needed.

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

Conciseness2/5

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

The description is overly terse at four words. While concise, it lacks substance and fails to add value beyond the tool name. It does not front-load key information or justify its existence as standalone guidance.

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

Completeness1/5

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

Given the tool's complexity (15 parameters, nested objects, no output schema), the description is grossly incomplete. It provides no context about return values, business logic, or relationships to other entities, rendering it nearly useless for accurate invocation.

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?

With 87% schema description coverage, the input schema already describes most parameters adequately. The description adds no additional semantic value beyond the schema, but per guidelines, the baseline is 3 when coverage is high.

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

Purpose2/5

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

The description simply states 'Create a planned course.' While it identifies the verb and resource, it fails to distinguish this tool from many sibling 'create_*' tools (e.g., create_course, create_course_variant). It lacks specifics on what a planned course is versus other entities.

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. The description offers no context about prerequisites, appropriate scenarios, or exclusions, which is a significant gap given the large set of sibling tools.

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