Skip to main content
Glama

delete_meeting_location

DestructiveIdempotent

Delete a specific meeting location for a course by providing its ID. Removes unwanted or outdated locations from the system.

Instructions

Delete a course location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the meeting location to delete

Implementation Reference

  • The handler function for the 'delete_meeting_location' tool. It accepts an 'id' parameter, calls apiDelete to DELETE /meeting_locations/:id, logs the response, and returns a formatted delete result.
    async ({ id }) => {
      try {
        const record = await apiDelete<EduframeRecord>(`/meeting_locations/${id}`);
        void logResponse("delete_meeting_location", { id }, record);
        return formatDelete(record, "meeting location");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for 'delete_meeting_location': requires a positive integer 'id' field describing the meeting location to delete.
    description: "Delete a course location.",
    annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
    inputSchema: { id: z.number().int().positive().describe("ID of the meeting location to delete") },
  • Registration of 'delete_meeting_location' tool via server.registerTool() with description and destructiveHint annotation.
    server.registerTool(
      "delete_meeting_location",
      {
        description: "Delete a course location.",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the meeting location to delete") },
      },
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/meeting_locations/${id}`);
          void logResponse("delete_meeting_location", { id }, record);
          return formatDelete(record, "meeting location");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The registerMeetingLocationTools function is included in the tools array, which is iterated to register all tools on the MCP server.
    registerMeetingLocationTools,
  • The apiDelete helper function used by the handler to perform the HTTP DELETE request to the Eduframe API.
    /**
     * Perform a DELETE request to remove a resource.
     *
     * @param path - API path, e.g. "/leads/1"
     */
    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);
    }
Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true, which clearly signal the delete nature. The description adds no further behavioral context beyond the basic action, but it does not contradict annotations. Minimal extra value.

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

Conciseness4/5

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

The description is a single short sentence without fluff. It is efficient for a simple tool, though the internal inconsistency (meeting vs course) detracts slightly.

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 one-parameter delete tool with no output schema, the description is mostly adequate but fails to specify the exact resource type (meeting vs course location). This missing clarity reduces completeness given the potential confusion with sibling tools.

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 provides full description for the single required parameter 'id' (100% coverage). The description adds no additional parameter meaning beyond what the schema already offers, so baseline 3 applies.

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

Purpose3/5

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

The description states the verb and resource ('Delete a course location'), but the tool name uses 'meeting location' while description says 'course location', creating confusion about the exact resource being deleted. This inconsistency diminishes clarity, especially since there is a separate sibling 'delete_course_location'.

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., delete_course_location). There are no explicit conditions or exclusions, leaving the agent to infer 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