Skip to main content
Glama

activate_teacher

Idempotent

Activate a teacher by providing their ID. This tool marks the teacher as active in the Eduframe system.

Instructions

Mark teacher as active

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the teacher

Implementation Reference

  • The 'activate_teacher' tool handler function. It takes an 'id' input, POSTs to /teachers/{id}/activate to mark a teacher as active, logs the response, and returns the formatted teacher record.
    server.registerTool(
      "activate_teacher",
      {
        description: "Mark teacher as active",
        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}/activate`, {});
          void logResponse("activate_teacher", { id }, record);
          return formatShow(record, "teacher");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Input schema for 'activate_teacher' - requires a positive integer 'id' field.
    {
      description: "Mark teacher as active",
      annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the teacher") },
  • Registration of 'activate_teacher' tool via server.registerTool() within registerTeacherTools().
    server.registerTool(
      "activate_teacher",
      {
        description: "Mark teacher as active",
        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}/activate`, {});
          void logResponse("activate_teacher", { id }, record);
          return formatShow(record, "teacher");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Top-level registration: registerTeacherTools is called from registerAllTools() in the tools index, which iterates over all tool registration functions.
    for (const register of tools) {
      register(server);
    }
  • The apiPost helper used by the handler to POST to /teachers/{id}/activate endpoint.
    export async function apiPost<T>(path: string, body: unknown): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "POST",
        headers: buildHeaders(token),
        body: JSON.stringify(body),
      });
    
      return handleResponse<T>(response);
    }
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds no additional behavioral context beyond 'Mark teacher as active', so it only moderately supplements the 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 communicates the essential purpose without unnecessary words.

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?

Given the tool's simplicity (one required parameter, idempotent, no output schema), the description is nearly complete. It does not address edge cases like what happens if the teacher is already active, but this is minor.

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 with a description for 'id'. The tool description adds no extra meaning beyond what is already provided in the schema, so baseline score 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 'Mark teacher as active' clearly states the verb (Mark) and resource (teacher as active), distinguishing it from the sibling 'deactivate_teacher'.

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 activating a teacher, but does not explicitly state when to use this tool versus alternatives, such as when a teacher is deactivated or already active.

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