Skip to main content
Glama
moneyforward-i

Admina MCP Server

update_identity_custom_field

Update an existing identity custom field. Modify its display name and unique code.

Instructions

Update an existing identity custom field configuration. Can modify field name and code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customFieldIdYesThe ID of the custom field to update
attributeNameNoDisplay label for the custom field
attributeCodeNoUnique identifier for the custom field. Must contain only lowercase letters, numbers, and underscores.

Implementation Reference

  • The main handler function that executes the update_identity_custom_field tool logic. It builds a request body from optional params (attributeName, attributeCode) and makes a PATCH API call to /identity/fields/custom/{customFieldId}.
    export async function updateIdentityCustomField(params: UpdateIdentityCustomFieldParams) {
      const client = getClient();
    
      const body: Record<string, unknown> = {};
    
      if (params.attributeName !== undefined) body.attributeName = params.attributeName;
      if (params.attributeCode !== undefined) body.attributeCode = params.attributeCode;
    
      return client.makePatchApiCall(`/identity/fields/custom/${params.customFieldId}`, body);
    }
  • Zod schema defining the input parameters: customFieldId (required number), attributeName (optional string), attributeCode (optional string matching lowercase letters, numbers, underscores).
    export const UpdateIdentityCustomFieldSchema = z.object({
      customFieldId: z.number().describe("The ID of the custom field to update"),
      attributeName: z.string().optional().describe("Display label for the custom field"),
      attributeCode: z
        .string()
        .optional()
        .describe("Unique identifier for the custom field. Must contain only lowercase letters, numbers, and underscores."),
    });
  • src/index.ts:278-282 (registration)
    Registration of the tool with name 'update_identity_custom_field', description, and inputSchema in the ListToolsRequestSchema handler.
    {
      name: "update_identity_custom_field",
      description: "Update an existing identity custom field configuration. Can modify field name and code.",
      inputSchema: zodToJsonSchema(UpdateIdentityCustomFieldSchema),
    },
  • src/index.ts:330-332 (registration)
    Tool handler registration in the toolHandlers map, which parses input via UpdateIdentityCustomFieldSchema and calls updateIdentityCustomField.
    update_identity_custom_field: async (input) =>
      updateIdentityCustomField(UpdateIdentityCustomFieldSchema.parse(input)),
    delete_identity_custom_field: async (input) =>
  • The makePatchApiCall method on AdminaApiClient that performs the actual PATCH HTTP request, used by the handler to update the identity custom field.
    public async makePatchApiCall<T>(
      endpoint: string,
      body: Record<string, unknown> = {},
      config: AxiosRequestConfig = {},
    ): Promise<T> {
      try {
        const url = `${this.ADMINA_API_BASE}/organizations/${this.organizationId}${endpoint}`;
    
        const response = await axios.patch(url, body, {
          headers: {
            Authorization: `Bearer ${this.apiKey}`,
            "Content-Type": "application/json",
            ...MCP_USAGE_TRACKING_HEADERS,
          },
          ...config,
        });
    
        return response.data as T;
      } catch (error: unknown) {
        if (error instanceof AxiosError) {
          throw createAdminaError(error.status ?? 500, error.response?.data);
        }
        throw createAdminaError(500, { errorId: "non_axios_error" });
      }
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It doesn't disclose whether the update is partial, idempotent, or requires specific permissions. Missing behavioral traits like side effects or response format.

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 (12 words), front-loading the action and key details. No wasted words, though additional context could be added without sacrificing conciseness.

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?

For a simple update tool with 3 parameters and no output schema, the description covers basic purpose but lacks usage guidelines and behavioral transparency, leaving gaps for an AI agent.

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%, so baseline is 3. Description mentions modifying 'field name and code', which maps to attributeName and attributeCode, but adds no meaning beyond the schema descriptions.

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

Purpose5/5

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

The description clearly states the action ('Update'), the resource ('identity custom field configuration'), and what can be modified ('field name and code'). It distinguishes from sibling tools like create and delete.

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 (e.g., create or delete), no prerequisites, and no when-not-to-use conditions. The description only implies basic context.

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/moneyforward-i/admina-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server