Skip to main content
Glama

get_custom_objects

Read-onlyIdempotent

Retrieve custom objects from Eduframe with pagination. Specify cursor for next page and per_page to control results per page.

Instructions

Get all custom objects

Input Schema

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

Implementation Reference

  • The handler function and registration for the 'get_custom_objects' tool. It registers the tool with schema (cursor, per_page input), calls apiList on /custom/objects, formats results with formatList, and appends nextCursor if present.
    export function registerCustomObjectTools(server: McpServer): void {
      server.registerTool(
        "get_custom_objects",
        {
          description: "Get all custom objects",
          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>("/custom/objects", { cursor, per_page });
            void logResponse("get_custom_objects", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "custom objects");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • Input schema defined inline in the registration call: cursor (optional string) and per_page (optional positive integer) for pagination.
    export function registerCustomObjectTools(server: McpServer): void {
      server.registerTool(
        "get_custom_objects",
        {
          description: "Get all custom objects",
          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>("/custom/objects", { cursor, per_page });
            void logResponse("get_custom_objects", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "custom objects");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • Registered via server.registerTool('get_custom_objects', ...) inside the registerCustomObjectTools function.
    export function registerCustomObjectTools(server: McpServer): void {
      server.registerTool(
        "get_custom_objects",
        {
          description: "Get all custom objects",
          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>("/custom/objects", { cursor, per_page });
            void logResponse("get_custom_objects", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "custom objects");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • Import of registerCustomObjectTools from ./custom_objects, which is later called in registerAllTools.
    import { registerCustomObjectTools } from "./custom_objects";
  • registerCustomObjectTools is included in the tools array, invoked by registerAllTools to register all tools on the MCP server.
    registerCustomObjectTools,
Behavior2/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 description does not need to repeat safety. However, it adds no behavioral context beyond the annotations, such as pagination behavior, potential empty results, or ordering. The description misses an opportunity to clarify that results are paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single phrase, 'Get all custom objects', which is very concise but lacks structure. It is front-loaded but does not include any additional sentences. While brevity is valued, it sacrifices useful detail.

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 tool has pagination parameters and no output schema, the description should at least mention that it returns a paginated list of custom objects. It does not explain what fields are returned or how to handle pagination. The description is insufficient for the tool's complexity.

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, with clear descriptions for cursor and per_page. The description 'Get all custom objects' does not add any additional meaning to these parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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 states 'Get all custom objects', which clearly indicates the verb and resource. However, 'all' may be misleading since pagination is supported via cursor and per_page parameters; the description does not clarify that it returns a paginated list. It distinguishes from siblings like get_custom_object_by_object_slug but not from get_custom_records.

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_custom_records or get_custom_object_by_object_slug. There is no mention of prerequisites, context, 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