Skip to main content
Glama

delete_affiliation

DestructiveIdempotent

Delete an affiliation record by specifying its ID to remove it from the system.

Instructions

Delete an affiliation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the affiliation to delete

Implementation Reference

  • Handler function for delete_affiliation tool. Calls apiDelete on /affiliations/{id}, logs the response, and formats the result using formatDelete.
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/affiliations/${id}`);
          void logResponse("delete_affiliation", { id }, record);
          return formatDelete(record, "affiliation");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Input schema for delete_affiliation: requires a positive integer 'id' parameter. Marked as destructive and idempotent.
    {
      description: "Delete an affiliation",
      annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the affiliation to delete") },
    },
  • Registration of delete_affiliation tool on the MCP server via registerTool(). Registered inside registerAffiliationTools() which is exported from src/tools/affiliations.ts.
    server.registerTool(
      "delete_affiliation",
      {
        description: "Delete an affiliation",
        annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the affiliation to delete") },
      },
      async ({ id }) => {
        try {
          const record = await apiDelete<EduframeRecord>(`/affiliations/${id}`);
          void logResponse("delete_affiliation", { id }, record);
          return formatDelete(record, "affiliation");
        } catch (error) {
          return formatError(error);
        }
      },
    );
Behavior3/5

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

Annotations already indicate destructiveHint and idempotentHint. The description adds no behavioral details beyond what annotations provide, but does not contradict them.

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 concise with one short sentence, though it lacks structure or additional details that could improve understanding.

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

Completeness2/5

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

No output schema; description does not mention return value, error handling, or differentiate from similar deletion tools, leaving gaps for an agent.

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% and the description does not add any meaning beyond the schema definition of the 'id' parameter.

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 an affiliation' clearly states the action and resource, but does not differentiate from the sibling 'delete_organization_affiliation', which could cause confusion.

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 like 'delete_organization_affiliation'; no exclusions or context provided.

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