Skip to main content
Glama

delete_planning_attendee

DestructiveIdempotent

Remove a teacher from a meeting or planning event by providing the attendee's ID.

Instructions

Remove a teacher from a meeting or planning event.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the planning attendee to delete

Implementation Reference

  • The handler function that executes the delete_planning_attendee tool logic. It accepts { id } from the input, calls apiDelete to DELETE /planning/attendees/{id}, logs the response, and returns a formatted delete result.
    async ({ id }) => {
      try {
        const record = await apiDelete<EduframeRecord>(`/planning/attendees/${id}`);
        void logResponse("delete_planning_attendee", { id }, record);
        return formatDelete(record, "planning attendee");
      } catch (error) {
        return formatError(error);
      }
    },
  • The input schema for delete_planning_attendee: requires id (positive integer) with description 'ID of the planning attendee to delete' and annotations marking it as destructive and idempotent.
    {
      description: "Remove a teacher from a meeting or planning event.",
      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the planning attendee to delete") },
    },
  • The server.registerTool call that registers 'delete_planning_attendee' with its schema, annotations, and handler.
    server.registerTool(
      "delete_planning_attendee",
      {
        description: "Remove a teacher from a meeting or planning event.",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the planning attendee to delete") },
      },
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/planning/attendees/${id}`);
          void logResponse("delete_planning_attendee", { id }, record);
          return formatDelete(record, "planning attendee");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The registerAllTools function iterates over all tool registrations including registerPlanningAttendeeTools which registers delete_planning_attendee.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
  • The apiDelete helper used by the handler to perform the DELETE HTTP request to /planning/attendees/{id}.
    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 provide destructiveHint=true and idempotentHint=true. The description adds context about what is removed (teacher from meeting/event) but does not disclose additional behavioral traits such as required permissions, cascading effects, or reversibility.

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, front-loaded sentence with no unnecessary words, efficiently conveying the tool's purpose.

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

Completeness5/5

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

For a simple delete operation with one parameter and annotations covering safety and idempotency, the description is complete. No output schema is needed for this straightforward tool.

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% coverage for its single parameter with a clear description. The tool description does not add further meaning beyond what the schema already 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 action ('Remove') and the resource ('a teacher from a meeting or planning event'), distinguishing it from sibling tools like 'delete_planning_event' which deletes the entire event.

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 implies usage for removing a teacher from a meeting or planning event but does not provide explicit guidance on when to use this tool versus alternatives (e.g., deleting the event itself or other removal methods).

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