Skip to main content
Glama

get_meeting

Read-onlyIdempotent

Retrieve a meeting record by its ID. Access meeting details from Eduframe.

Instructions

Get an meeting record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the meeting to retrieve

Implementation Reference

  • The handler/execution function for the get_meeting tool. It calls apiGet on /meetings/{id}, logs the response, and formats the result using formatShow.
    async ({ id }) => {
      try {
        const record = await apiGet<EduframeRecord>(`/meetings/${id}`);
        void logResponse("get_meeting", { id }, record);
        return formatShow(record, "meeting");
      } catch (error) {
        return formatError(error);
      }
    },
  • The schema/metadata for the get_meeting tool, defining description, annotations, and input schema (a required positive integer 'id').
    {
      description: "Get an meeting record",
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the meeting to retrieve") },
    },
  • Registration of the get_meeting tool with the MCP server via server.registerTool in the registerMeetingTools function.
    server.registerTool(
      "get_meeting",
      {
        description: "Get an meeting record",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the meeting to retrieve") },
      },
      async ({ id }) => {
        try {
          const record = await apiGet<EduframeRecord>(`/meetings/${id}`);
          void logResponse("get_meeting", { id }, record);
          return formatShow(record, "meeting");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The registerMeetingTools function that groups all meeting-related tool registrations, including get_meeting.
    export function registerMeetingTools(server: McpServer): void {
      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);
          }
        },
      );
    
      server.registerTool(
        "get_meeting",
        {
          description: "Get an meeting record",
          annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
          inputSchema: { id: z.number().int().positive().describe("ID of the meeting to retrieve") },
        },
        async ({ id }) => {
          try {
            const record = await apiGet<EduframeRecord>(`/meetings/${id}`);
            void logResponse("get_meeting", { id }, record);
            return formatShow(record, "meeting");
          } catch (error) {
            return formatError(error);
          }
        },
      );
    
      server.registerTool(
        "delete_meeting",
        {
          description: "Delete a meeting.",
          annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
          inputSchema: { id: z.number().int().positive().describe("ID of the meeting to delete") },
        },
        async ({ id }) => {
          try {
            const record = await apiDelete<EduframeRecord>(`/meetings/${id}`);
            void logResponse("delete_meeting", { id }, record);
            return formatDelete(record, "meeting");
          } catch (error) {
            return formatError(error);
          }
        },
      );
    }
  • The apiGet helper function used by the get_meeting handler to make the actual HTTP GET request to the Eduframe API.
    export async function apiGet<T>(path: string, query?: Record<string, QueryValue>): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path, query);
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: buildHeaders(token),
      });
    
      return handleResponse<T>(response);
    }
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no extra behavioral context, such as what the response contains or any side effects. Since annotations cover the main traits, the description is minimally adequate.

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 only one sentence and contains no unnecessary words. It is front-loaded and efficient, though the minor grammatical error does not impact conciseness.

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 get-by-id operation with good annotations, the description is just adequate. It does not explain the return format, permissions, or typical usage, but the simplicity reduces the need for extensive detail.

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 for the single parameter 'id'. The description does not add any meaning beyond what the schema already provides. Baseline score of 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 uses the verb 'Get' and explicitly names the resource 'meeting record', making the purpose clear. It distinguishes from siblings like get_meeting_location and get_meetings_by_planned_course_id because it retrieves a single meeting by ID. However, the grammatical error 'an meeting' slightly detracts from 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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_meetings_by_planned_course_id). There is no mention of context, prerequisites, or limitations.

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