Skip to main content
Glama

delete_meeting

DestructiveIdempotent

Delete a meeting by providing its unique ID to remove it from the system.

Instructions

Delete a meeting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the meeting to delete

Implementation Reference

  • The handler for the delete_meeting tool. It calls apiDelete on /meetings/{id}, logs the response, and formats the result using formatDelete.
    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);
        }
      },
  • Input schema for delete_meeting: expects a positive integer 'id' field representing the meeting to delete.
    {
      description: "Delete a meeting.",
      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the meeting to delete") },
  • Registration of the delete_meeting tool via server.registerTool inside the registerMeetingTools function.
      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 registerAllTools function that ultimately calls registerMeetingTools (and thus registers delete_meeting) on the server.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
  • The apiDelete helper function used by the handler to send an HTTP DELETE request to the Eduframe API.
    export async function apiDelete<T>(path: string): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "DELETE",
        headers: buildHeaders(token),
      });
    
      return handleResponse<T>(response);
    }
Behavior2/5

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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate destructiveHint=true and idempotentHint=true, but the description does not elaborate on permanence, cascading 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 with no unnecessary 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?

Given the low complexity (one parameter, no output schema, annotations present), the description provides the minimum necessary to understand what the tool does, but fails to offer additional context such as confirmation or irreversibility beyond annotations.

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 covers 100% of the single parameter. The description adds no extra meaning beyond what the schema already describes (ID of the meeting to delete).

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 'Delete a meeting.' clearly states the action and resource. It is specific but does not distinguish between sibling delete tools (e.g., delete_meeting_location) beyond the tool name.

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 such as other delete tools. No context about prerequisites or conditions is given.

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