Skip to main content
Glama

delete_certificate_from_program_enrollment

Idempotent

Delete a certificate from a program enrollment by providing the enrollment ID.

Instructions

Deletes a certificate from a program enrollment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the program enrollment

Implementation Reference

  • Registration of the 'delete_certificate_from_program_enrollment' tool via server.registerTool(). Defines description, annotations, inputSchema (id), and the async handler that calls apiPost on /program/enrollments/${id}/delete_certificate.
    server.registerTool(
      "delete_certificate_from_program_enrollment",
      {
        description: "Deletes a certificate from a program enrollment",
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the program enrollment") },
      },
      async ({ id }) => {
        try {
          const record = await apiPost<EduframeRecord>(`/program/enrollments/${id}/delete_certificate`, {});
          void logResponse("delete_certificate_from_program_enrollment", { id }, record);
          return formatShow(record, "program enrollment");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The handler async function that executes the tool logic: calls apiPost to the delete_certificate endpoint and returns the formatted record.
    async ({ id }) => {
      try {
        const record = await apiPost<EduframeRecord>(`/program/enrollments/${id}/delete_certificate`, {});
        void logResponse("delete_certificate_from_program_enrollment", { id }, record);
        return formatShow(record, "program enrollment");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema definition for the tool: requires a single 'id' field (positive integer).
      inputSchema: { id: z.number().int().positive().describe("ID of the program enrollment") },
    },
Behavior2/5

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds no behavioral details beyond the literal action. The term 'Deletes' may contradict destructiveHint=false, but if it is a soft delete, the description does not clarify. Minimal added value.

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, no redundancy, and perfectly sized for the tool's simplicity.

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 tool with one parameter, no output schema, and annotations present, the description sufficiently explains the action without missing critical details.

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 the parameter 'id' described as 'ID of the program enrollment'. The description does not provide additional semantic meaning beyond the schema, so baseline 3 applies.

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 'Deletes' and the resource 'a certificate from a program enrollment'. It distinguishes from sibling tools like award_certificate_to_program_enrollment or cancel_program_enrollment.

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 on when to use this tool versus alternatives such as award_certificate_to_program_enrollment or cancel_program_enrollment. The agent is left without context for selecting the correct tool among many sibling tools.

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