Skip to main content
Glama

deactivate_teacher

Idempotent

Mark a teacher as inactive by providing their ID. Useful for managing teacher records when they leave or are no longer active.

Instructions

Mark teacher as inactive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the teacher

Implementation Reference

  • Registration and handler for the 'deactivate_teacher' tool. Calls apiPost to deactivate a teacher by ID and returns formatted result.
    server.registerTool(
      "deactivate_teacher",
      {
        description: "Mark teacher as inactive",
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the teacher") },
      },
      async ({ id }) => {
        try {
          const record = await apiPost<EduframeRecord>(`/teachers/${id}/deactivate`, {});
          void logResponse("deactivate_teacher", { id }, record);
          return formatShow(record, "teacher");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Entry point: registerTeacherTools is called via registerAllTools loop to register the deactivate_teacher tool on the MCP server.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
  • Input schema for deactivate_teacher: requires an integer id field.
      description: "Mark teacher as inactive",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the teacher") },
    },
Behavior3/5

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

Annotations already indicate this is a non-destructive, idempotent mutation. The description adds no behavioral details beyond stating the effect. It does not contradict annotations.

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 that front-loads the core purpose. No unnecessary words or details.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description is mostly sufficient. It could mention reversibility or side effects, but the core action is clear.

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%; the single parameter 'id' is described in the schema as 'ID of the teacher'. The description adds no additional semantic meaning beyond what the schema 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 'Mark teacher as inactive' clearly states the action (mark), the resource (teacher), and the result (inactive). It distinguishes from the sibling tool 'activate_teacher' which performs the opposite action.

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?

The description provides no guidance on when to use this tool versus alternatives like 'activate_teacher'. No when/when-not or contextual advice 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