Skip to main content
Glama

get_planning_locations

Read-onlyIdempotent

Retrieve a paginated list of available planning locations. Use cursor and per_page parameters to control the number of results.

Instructions

Get all locations that are available

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for fetching the next page of results
per_pageNoNumber of results per page (default: 25)

Implementation Reference

  • Tool registration and handler for 'get_planning_locations'. Registers the tool with an input schema (cursor, per_page) and the async handler that calls the Eduframe API endpoint '/planning/locations'.
    export function registerPlanningLocationTools(server: McpServer): void {
      server.registerTool(
        "get_planning_locations",
        {
          description: "Get all locations that are available",
          annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
          inputSchema: {
            cursor: z.string().optional().describe("Cursor for fetching the next page of results"),
            per_page: z.number().int().positive().optional().describe("Number of results per page (default: 25)"),
          },
        },
        async ({ cursor, per_page }) => {
          try {
            const result = await apiList<EduframeRecord>("/planning/locations", { cursor, per_page });
            void logResponse("get_planning_locations", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "planning locations");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
    }
  • The async handler function for 'get_planning_locations'. Calls apiList('/planning/locations', ...), logs the response, and formats the result using formatList.
    async ({ cursor, per_page }) => {
      try {
        const result = await apiList<EduframeRecord>("/planning/locations", { cursor, per_page });
        void logResponse("get_planning_locations", { cursor, per_page }, result);
        const toolResult = formatList(result.records, "planning locations");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema definition for 'get_planning_locations'. Accepts optional 'cursor' (string) and 'per_page' (positive integer) parameters with descriptions.
    {
      description: "Get all locations that are available",
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
      inputSchema: {
        cursor: z.string().optional().describe("Cursor for fetching the next page of results"),
        per_page: z.number().int().positive().optional().describe("Number of results per page (default: 25)"),
      },
  • Import of registerPlanningLocationTools in the central tools registry.
    import { registerPlanningLocationTools } from "./planning_locations";
  • Registration of registerPlanningLocationTools in the tools array that is iterated over in registerAllTools.
    registerPlanningLocationTools,
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds no further behavioral context (e.g., pagination limits, availability filtering) but 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that is front-loaded and contains no unnecessary words. It appropriately summarizes the tool's core function for a simple listing operation.

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

Completeness3/5

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

Given the tool's simplicity and the presence of comprehensive schema descriptions and annotations, the description is adequate but could be improved by clarifying what 'available' means or hinting at the planning-specific context. It does not explain return values, but no output schema exists.

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% description coverage for both parameters (cursor and per_page), so the baseline is 3. The description does not add any additional meaning or context for these parameters.

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 uses 'Get' as the verb and 'locations' as the resource, with 'all that are available' specifying the scope. It is clear but does not explicitly mention the 'planning' context, relying on the tool name. It distinguishes from sibling tools like get_meeting_locations and get_course_locations only via the name, not the description.

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 is provided on when to use this tool versus alternatives such as get_meeting_locations or get_course_locations. There is no mention of prerequisites, use cases, or when not to use it.

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