Skip to main content
Glama

get_category

Read-onlyIdempotent

Retrieve a specific category record by providing its unique ID. Use to access category details from the Eduframe system.

Instructions

Get a category record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the categorie to retrieve

Implementation Reference

  • The 'get_category' tool handler function. It calls apiGet('/categories/{id}') to fetch a single category record, logs the response, and formats the result using formatShow().
    server.registerTool(
      "get_category",
      {
        description: "Get a category record",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the categorie to retrieve") },
      },
      async ({ id }) => {
        try {
          const record = await apiGet<EduframeRecord>(`/categories/${id}`);
          void logResponse("get_category", { id }, record);
          return formatShow(record, "categorie");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Input schema for 'get_category' tool. Requires a positive integer 'id' parameter with description 'ID of the categorie to retrieve'.
    {
      description: "Get a category record",
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
      inputSchema: { id: z.number().int().positive().describe("ID of the categorie to retrieve") },
  • Registration of 'get_category' tool via server.registerTool() with readOnlyHint=true, destructiveHint=false, idempotentHint=true annotations.
    server.registerTool(
      "get_category",
      {
        description: "Get a category record",
        annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
        inputSchema: { id: z.number().int().positive().describe("ID of the categorie to retrieve") },
      },
      async ({ id }) => {
        try {
          const record = await apiGet<EduframeRecord>(`/categories/${id}`);
          void logResponse("get_category", { id }, record);
          return formatShow(record, "categorie");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Top-level registration: registerAllTools() iterates over all tool registration functions including registerCategorieTools which registers 'get_category'.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
  • The apiGet() helper function used by the 'get_category' handler to perform a GET request to the Eduframe API.
    export async function apiGet<T>(path: string, query?: Record<string, QueryValue>): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path, query);
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: buildHeaders(token),
      });
    
      return handleResponse<T>(response);
    }
Behavior3/5

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

The description is consistent with annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) but adds no additional behavioral context beyond what annotations already provide.

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 a single sentence that is efficient with words, though it is somewhat under-specified. It is not verbose and gets straight to the point.

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?

Given the lack of an output schema, the description does not compensate by explaining return values or behavior on error, such as what happens if the ID does not exist.

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 description coverage is 100%, and the tool description adds no extra meaning about the 'id' parameter beyond the schema's description.

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 'Get a category record' clearly states the action (get) and resource (category record), distinguishing it from sibling tools like 'get_categories' (list) and 'create_category' (create).

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 vs alternatives. There is no mention of prerequisites, context, or when not to use it, leaving the agent to infer from the tool name alone.

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