Skip to main content
Glama

get_referrals

Read-onlyIdempotent

Retrieve all referral records with optional pagination using a cursor and per_page parameter.

Instructions

Get all referral records

Input Schema

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

Implementation Reference

  • The async handler function that calls the API to fetch referrals, logs the response, formats the result, and returns it with optional pagination cursor.
      async ({ cursor, per_page }) => {
        try {
          const result = await apiList<EduframeRecord>("/referrals", { cursor, per_page });
          void logResponse("get_referrals", { cursor, per_page }, result);
          const toolResult = formatList(result.records, "referrals");
          if (result.nextCursor) {
            toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
          }
          return toolResult;
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • The input schema using Zod, defining optional 'cursor' (string) and 'per_page' (positive integer) parameters.
    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)"),
    },
  • The registration function 'registerReferralTools' that calls server.registerTool() with the name 'get_referrals', description, annotations, input schema, and handler.
    export function registerReferralTools(server: McpServer): void {
      server.registerTool(
        "get_referrals",
        {
          description: "Get all referral records",
          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>("/referrals", { cursor, per_page });
            void logResponse("get_referrals", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "referrals");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • The top-level registration entry point that iterates over all tool registrations (including registerReferralTools) and calls each with the server instance.
    export function registerAllTools(server: McpServer): void {
      for (const register of tools) {
        register(server);
      }
    }
Behavior2/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint, so the description adds no behavioral context beyond 'get'. It does not mention pagination, rate limits, or that the tool returns a list. The description provides no additional value over 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.

Conciseness4/5

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

The description is a single, concise sentence with no wasted words. However, it is so brief that it borders on under-description, but no superfluous content earns a 4.

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?

The tool has two optional pagination parameters and no output schema. The description does not explain the response format (e.g., list of referrals, paginated results), leaving a significant gap for an agent to understand the tool's behavior. Completeness is lacking.

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, so the description adds no extra meaning. Baseline 3 is appropriate as the schema carries the load.

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 referral records' clearly indicates the action (get) and resource (referral records), distinguishing it from other get_* tools. However, it does not clarify what constitutes a referral record, leaving a minor gap in specificity.

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?

No explicit guidance on when to use this tool versus alternatives, but the tool's purpose is straightforward and there are no sibling tools with similar referral functionality, so usage is implied. A brief note on pagination or filtering context would improve clarity.

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