Skip to main content
Glama

get_payment_options

Read-onlyIdempotent

Retrieve all payment option records from Eduframe. Supports pagination with cursor and per_page parameters.

Instructions

Get all payment option 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 executes the tool logic. It calls apiList('/payment_options') with cursor and per_page parameters, logs the response, formats the result using formatList, and appends a nextCursor link if pagination is available.
    async ({ cursor, per_page }) => {
      try {
        const result = await apiList<EduframeRecord>("/payment_options", { cursor, per_page });
        void logResponse("get_payment_options", { cursor, per_page }, result);
        const toolResult = formatList(result.records, "payment options");
        if (result.nextCursor) {
          toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
        }
        return toolResult;
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for get_payment_options: optional cursor string and optional per_page positive integer.
    {
      description: "Get all payment option 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)"),
      },
  • Registration of the tool via server.registerTool with name 'get_payment_options', description, annotations, input schema, and handler function.
    export function registerPaymentOptionTools(server: McpServer): void {
      server.registerTool(
        "get_payment_options",
        {
          description: "Get all payment option 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>("/payment_options", { cursor, per_page });
            void logResponse("get_payment_options", { cursor, per_page }, result);
            const toolResult = formatList(result.records, "payment options");
            if (result.nextCursor) {
              toolResult.content.push({ type: "text", text: `\nNext page cursor: ${result.nextCursor}` });
            }
            return toolResult;
          } catch (error) {
            return formatError(error);
          }
        },
      );
  • The apiList helper function used by the handler to perform a GET request to '/payment_options' with cursor-based pagination support.
    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 };
    }
  • The formatList helper function used to format the list of payment option records into a human-readable text response.
    export function formatList(records: EduframeRecord[], resourceName: string): CallToolResult {
      if (records.length === 0) {
        return {
          content: [
            {
              type: "text",
              text: `No ${resourceName} found.`,
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: `Found ${records.length} ${resourceName}:\n\n${formatJSON(records)}${RESPONSE_LOG_HINT}`,
          },
        ],
      };
    }
Behavior3/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds no additional behavioral context beyond the pagination parameters implied by the schema.

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

Conciseness5/5

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

A single sentence that directly states the tool's purpose with no extraneous words. Perfectly concise.

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

Completeness4/5

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

For a simple paginated list tool, the description combined with schema and annotations is sufficient. No output schema exists, but the tool's purpose (get records) doesn't require detailed return value documentation.

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 covers 100% of parameters with descriptions. The tool description adds no extra meaning beyond what the schema provides, so baseline 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 "Get all payment option records" clearly states a specific verb and resource. However, it does not differentiate from many sibling get_ tools, which is a minor gap.

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 like get_payment or get_payment_methods. The context of pagination is implied but not explicitly stated as a use case.

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