Skip to main content
Glama

get_associations_of_object

Read-onlyIdempotent

Retrieve all associations linked to a system object by providing its object type ID. Optionally paginate results with cursor and per_page parameters.

Instructions

Get all associations of a system object

Input Schema

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

Implementation Reference

  • Handler function that executes the tool logic: calls the Eduframe API endpoint /custom/{object_type}/associations, logs the response, formats the list result, and appends pagination cursor if available.
    async ({ object_type, cursor, per_page }) => {
      try {
        const result = await apiList<EduframeRecord>(`/custom/${object_type}/associations`, { cursor, per_page });
        void logResponse("get_associations_of_object", { object_type, cursor, per_page }, result);
        const toolResult = formatList(result.records, "custom associations");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema with Zod validation accepting object_type (required positive int), cursor (optional string), and per_page (optional positive int).
    {
      description: "Get all associations of a system object",
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
      inputSchema: {
        object_type: z.number().int().positive().describe("ID of the parent resource"),
        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)"),
      },
  • Registration of the tool via server.registerTool with the name 'get_associations_of_object', its schema, and handler.
      server.registerTool(
        "get_associations_of_object",
        {
          description: "Get all associations of a system object",
          annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true },
          inputSchema: {
            object_type: z.number().int().positive().describe("ID of the parent resource"),
            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 ({ object_type, cursor, per_page }) => {
          try {
            const result = await apiList<EduframeRecord>(`/custom/${object_type}/associations`, { cursor, per_page });
            void logResponse("get_associations_of_object", { object_type, cursor, per_page }, result);
            const toolResult = formatList(result.records, "custom associations");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
    }
  • The registration aggregator that collects registerCustomAssociationTools (along with all other tool registrations) and calls each one in registerAllTools.
    const tools: Array<(server: McpServer) => void> = [
      registerAccountTools,
      registerAffiliationTools,
      registerAttendanceTools,
      registerAuthenticationTools,
      registerCatalogProductTools,
      registerCatalogVariantTools,
      registerCategorieTools,
      registerCertificateTools,
      registerCommentTools,
      registerCourseLocationTools,
      registerCourseTabTools,
      registerCourseVariantTools,
      registerCourseTools,
      registerCreditCategorieTools,
      registerCreditTools,
      registerCustomAssociationTools,
      registerCustomFieldOptionTools,
      registerCustomObjectTools,
      registerCustomRecordTools,
      registerDiscountCodeTools,
      registerEditionDescriptionSectionTools,
      registerEducatorTools,
      registerEmailTools,
      registerEnrollmentTools,
      registerGradeTools,
      registerInvoiceVatTools,
      registerInvoiceTools,
      registerLabelTools,
      registerLeadTools,
      registerMaterialGroupTools,
      registerMaterialTools,
      registerMeetingLocationTools,
      registerMeetingTools,
      registerOrderTools,
      registerOrganizationTools,
      registerPaymentMethodTools,
      registerPaymentOptionTools,
      registerPaymentTools,
      registerPlannedCourseTools,
      registerPlanningAttendeeTools,
      registerPlanningConflictTools,
      registerPlanningEventTools,
      registerPlanningLocationTools,
      registerPlanningMaterialTools,
      registerPlanningRequiredTeacherGroupAttendeeTools,
      registerPlanningTeacherTools,
      registerProgramEditionTools,
      registerProgramElementTools,
      registerProgramEnrollmentTools,
      registerProgramPersonalProgramElementTools,
      registerProgramProgramTools,
      registerReferralTools,
      registerSignupQuestionTools,
      registerTaskTools,
      registerTeacherEnrollmentTools,
      registerTeacherRoleTools,
      registerTeacherTools,
      registerTheseTools,
      registerUserTools,
      registerWebhookNotificationTools,
      registerWebhookTools,
    ];
    
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
  • The apiList helper function used by the handler to make the paginated GET request to the Eduframe API and return typed records with nextCursor.
    export async function apiList<T>(path: string, query?: Record<string, QueryValue>): Promise<ListResult<T>> {
      const { token } = getConfig();
      const url = buildUrl(path, query);
    
      const response = await fetch(url.toString(), {
        method: "GET",
        headers: buildHeaders(token),
      });
    
      await checkResponse(response);
    
      const records = (await response.json()) as T[];
      const nextCursor = parseNextCursor(response.headers.get("Link"));
    
      return { records, nextCursor };
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds no behavioral context beyond that, such as pagination behavior or what constitutes an 'association'.

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?

A single, concise sentence with no redundancy. However, it is extremely brief and could benefit from a bit more detail without becoming verbose.

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?

No output schema exists, and the description does not hint at the return structure. For a generic tool with three parameters, basic pagination and result format context would improve completeness.

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% with clear descriptions for all three parameters (object_type, cursor, per_page). The description does not add additional meaning beyond the schema.

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 'Get all associations of a system object' indicates the action (get) and target (associations), but 'system object' is vague and the title is null. It distinguishes from siblings by focusing on associations rather than specific entities.

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 versus alternatives like get_course or get_user. No mention of prerequisites or expected context for object_type.

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