Skip to main content
Glama

get_meetings_by_planned_course_id

Read-onlyIdempotent

Retrieve all meeting records for a specific planned course by providing its ID.

Instructions

Get all meeting records of a planned course

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
planned_course_idYesID of the parent resource
cursorNoCursor for fetching the next page of results
per_pageNoNumber of results per page (default: 25)
sortNoSort the results. Can change order by using `<sort_by>:<direction>` where `<direction>` is either `asc` or `desc`

Implementation Reference

  • The handler function for get_meetings_by_planned_course_id. It calls apiList with the path `/planned_courses/${planned_course_id}/meetings`, passing cursor, per_page, and sort params, then formats and returns the list result.
    async ({ planned_course_id, cursor, per_page, sort }) => {
      try {
        const result = await apiList<EduframeRecord>(`/planned_courses/${planned_course_id}/meetings`, {
          cursor,
          per_page,
          sort,
        });
        void logResponse("get_meetings_by_planned_course_id", { planned_course_id, cursor, per_page, sort }, result);
        const toolResult = formatList(result.records, "meetings");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for the get_meetings_by_planned_course_id tool. Defines planned_course_id (required number), cursor (optional string), per_page (optional number), and sort (optional array of enum values).
    inputSchema: {
      planned_course_id: z.number().int().positive().describe("ID of the parent resource"),
      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)"),
      sort: z
        .array(z.enum(["start_date_time:asc", "start_date_time:desc", "name:asc", "name:desc"]))
        .optional()
        .describe(
          "Sort the results. Can change order by using `<sort_by>:<direction>` where `<direction>` is either `asc` or `desc`",
        ),
    },
  • Registration of the 'get_meetings_by_planned_course_id' tool via server.registerTool(), with description and annotations.
    server.registerTool(
      "get_meetings_by_planned_course_id",
      {
        description: "Get all meeting records of a planned course",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: {
          planned_course_id: z.number().int().positive().describe("ID of the parent resource"),
          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)"),
          sort: z
            .array(z.enum(["start_date_time:asc", "start_date_time:desc", "name:asc", "name:desc"]))
            .optional()
            .describe(
              "Sort the results. Can change order by using `<sort_by>:<direction>` where `<direction>` is either `asc` or `desc`",
            ),
        },
      },
      async ({ planned_course_id, cursor, per_page, sort }) => {
        try {
          const result = await apiList<EduframeRecord>(`/planned_courses/${planned_course_id}/meetings`, {
            cursor,
            per_page,
            sort,
          });
          void logResponse("get_meetings_by_planned_course_id", { planned_course_id, cursor, per_page, sort }, result);
          const toolResult = formatList(result.records, "meetings");
          if (result.nextCursor) {
            toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
          }
          return toolResult;
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The apiList helper function used by the handler to perform the GET request to the Eduframe API with cursor-based pagination support.
    export async function apiList<T>(path: string, query?: Record<string, QueryValue>): Promise<ListResult<T>> {
      const { token } = getConfig();
      const url = buildUrl(path, query);
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: buildHeaders(token),
      });
    
      await checkResponse(response);
    
      const records = (await response.json()) as T[];
      const nextCursor = parseNextCursor(response.headers.get("Link"));
    
      return { records, nextCursor };
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description ('Get all meeting records') is consistent but adds no new behavioral traits beyond annotations.

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 sentence, front-loaded with the action verb, no redundant words. Efficient and clear.

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

Completeness4/5

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

For a simple read-only tool with well-documented params and safety annotations, the description is mostly complete. It doesn't explicitly mention pagination or sorting, but these are covered in the input schema.

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 descriptions for all 4 parameters. The tool description does not add any additional semantic information beyond what the schema provides.

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

Purpose5/5

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

The description clearly states the verb 'Get' and resource 'meeting records of a planned course', which distinguishes it from sibling tools like get_meeting (individual meeting) and get_meeting_locations (locations).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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 vs alternatives or any prerequisites. However, the tool is specific enough that its purpose implies usage context.

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