Skip to main content
Glama
moneyforward-i

Admina MCP Server

delete_identity_custom_field

Delete an identity custom field from your organization by providing its ID. Removes the custom field definition permanently.

Instructions

Delete an identity custom field for an organization. Removes a custom field definition from the organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customFieldIdYesThe ID of the custom field to delete. Make sure user wants to delete an identity custom field and not a device custom field

Implementation Reference

  • The handler function that executes the tool logic. It calls the Admina API DELETE endpoint `/identity/fields/custom/{customFieldId}` to delete an identity custom field.
    export async function deleteIdentityCustomField(params: DeleteIdentityCustomFieldParams) {
      const client = getClient();
      return client.makeDeleteApiCall(`/identity/fields/custom/${params.customFieldId}`);
    }
  • Zod schema defining the input: a required `customFieldId` (number) with a description clarifying it's for identity (not device) custom fields.
    export const DeleteIdentityCustomFieldSchema = z.object({
      customFieldId: z
        .number()
        .describe(
          "The ID of the custom field to delete. Make sure user wants to delete an identity custom field and not a device custom field",
        ),
    });
  • src/index.ts:283-288 (registration)
    Tool registration in the MCP server's list of tools, with name 'delete_identity_custom_field', description, and input schema.
    {
      name: "delete_identity_custom_field",
      description:
        "Delete an identity custom field for an organization. Removes a custom field definition from the organization.",
      inputSchema: zodToJsonSchema(DeleteIdentityCustomFieldSchema),
    },
  • src/index.ts:332-333 (registration)
    Tool handler mapping in the toolHandlers record, wiring the tool name to the function with schema parsing.
    delete_identity_custom_field: async (input) =>
      deleteIdentityCustomField(DeleteIdentityCustomFieldSchema.parse(input)),
  • Re-export from the tools barrel index file, making the module publicly accessible.
    export * from "./deleteIdentityCustomField.js";
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the action is destructive ('removes a custom field definition') but lacks explicit details about irreversibility, cascading effects on identities, or required permissions.

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?

The description consists of two concise sentences with no unnecessary information. It is front-loaded with the action and resource.

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?

For a simple delete tool with one parameter and no output schema, the description covers the basic purpose but omits important context about idempotency, error behavior (e.g., field not found), and implications for existing data.

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% coverage with a detailed parameter description. The tool description does not add new meaning beyond the schema's description of the parameter, so baseline 3 is appropriate.

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 ('delete') and the resource ('identity custom field'), and distinguishes from sibling 'delete_device_custom_field' by specifying 'identity'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parameter description warns the user to ensure they are deleting an identity rather than a device custom field, providing a clear differentiator from the sibling tool. However, it does not specify prerequisites or when not to use.

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