Skip to main content
Glama

update_custom_record

Idempotent

Update specific custom records by ID for a parent resource, modifying fields like display name, active status, and custom properties.

Instructions

Update a custom record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_slugYesID of the parent resource
idYesID of the custom record to update
activeNoWhether the custom record is active.
display_nameNoThe display name of the custom record.
propertiesNo

Implementation Reference

  • The handler function for the update_custom_record tool. It receives object_slug, id, and optional body fields (active, display_name, properties), destructures id from the rest of body, calls apiPatch to PATCH /custom/objects/{object_slug}/records/{id}, logs the response, and formats the result using formatUpdate.
    async ({ object_slug, id, ...body }) => {
      try {
        const record = await apiPatch<EduframeRecord>(`/custom/objects/${object_slug}/records/${record_id}`, body);
        void logResponse("update_custom_record", { object_slug, id, ...body }, record);
        return formatUpdate(record, "custom record");
      } catch (error) {
        return formatError(error);
      }
    },
  • Input schema for update_custom_record. Defines required parameters: object_slug (number), id (number), and optional fields: active (boolean), display_name (string), properties (record of unknown).
      inputSchema: {
        object_slug: z.number().int().positive().describe("ID of the parent resource"),
        id: z.number().int().positive().describe("ID of the custom record to update"),
        active: z.boolean().optional().describe("Whether the custom record is active."),
        display_name: z.string().optional().describe("The display name of the custom record."),
        properties: z.record(z.unknown()).optional(),
      },
    },
  • Registration of the update_custom_record tool via server.registerTool(name, schema, handler). The annotations indicate it is not read-only (readOnlyHint: false), not destructive (destructiveHint: false), and idempotent (idempotentHint: true).
    server.registerTool(
      "update_custom_record",
      {
        description: "Update a custom record",
        annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true },
        inputSchema: {
          object_slug: z.number().int().positive().describe("ID of the parent resource"),
          id: z.number().int().positive().describe("ID of the custom record to update"),
          active: z.boolean().optional().describe("Whether the custom record is active."),
          display_name: z.string().optional().describe("The display name of the custom record."),
          properties: z.record(z.unknown()).optional(),
        },
      },
      async ({ object_slug, id, ...body }) => {
        try {
          const record = await apiPatch<EduframeRecord>(`/custom/objects/${object_slug}/records/${record_id}`, body);
          void logResponse("update_custom_record", { object_slug, id, ...body }, record);
          return formatUpdate(record, "custom record");
        } catch (error) {
          return formatError(error);
        }
      },
    );
  • Import of registerCustomRecordTools from ./custom_records module, which registers update_custom_record among other custom record tools.
    import { registerCustomRecordTools } from "./custom_records";
  • The apiPatch helper function used by the handler to make the PATCH HTTP request to the Eduframe API endpoint /custom/objects/{object_slug}/records/{id}.
    export async function apiPatch<T>(path: string, body: unknown): Promise<T> {
      const { token } = getConfig();
      const url = buildUrl(path);
    
      const response = await fetch(url.toString(), {
        method: "PATCH",
        headers: buildHeaders(token),
        body: JSON.stringify(body),
      });
    
      return handleResponse<T>(response);
    }
Behavior2/5

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

Annotations indicate idempotentHint=true and no destructive behavior, but the description does not add any behavioral context such as whether partial updates are supported or how the 'properties' field behaves. It misses an opportunity to clarify side effects.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specified and does not convey useful information beyond the tool name. Brevity without substance is not concise.

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

Completeness1/5

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

Given the complexity of having 5 parameters including a nested object, and the absence of any output schema, the description is severely lacking. It does not explain return values, update behavior, or constraints, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the baseline is not elevated. The description does not add any meaning beyond the schema; it fails to explain the 'properties' parameter which lacks a schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a custom record' clearly states the verb (update) and resource (custom record), but it is generic and does not distinguish from other update tools for different entities. It suffices but lacks specificity about what can be updated.

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 like create_custom_record or delete_custom_record. There is no context on prerequisites or typical scenarios.

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