Skip to main content
Glama
moneyforward-i

Admina MCP Server

delete_device_custom_field

Deletes a device custom field configuration by removing its definition from the organization. Provide the custom field ID to perform the removal.

Instructions

Delete a device custom field configuration. 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 a device custom field and not an identity custom field

Implementation Reference

  • The main handler function that executes the delete_device_custom_field tool logic. It calls the Admina API DELETE /fields/custom/{customFieldId} endpoint.
    export async function deleteDeviceCustomField(params: DeleteDeviceCustomFieldParams) {
      const client = getClient();
      return client.makeDeleteApiCall(`/fields/custom/${params.customFieldId}`);
    }
  • Zod schema defining the input for delete_device_custom_field. Expects a required numeric 'customFieldId'.
    export const DeleteDeviceCustomFieldSchema = z.object({
      customFieldId: z
        .number()
        .describe(
          "The ID of the custom field to delete. Make sure user wants to delete a device custom field and not an identity custom field",
        ),
    });
  • src/index.ts:154-159 (registration)
    Tool registration in the list of tools with name 'delete_device_custom_field', description, and inputSchema.
    {
      name: "delete_device_custom_field",
      description:
        "Delete a device custom field configuration. Removes a custom field definition from the organization.",
      inputSchema: zodToJsonSchema(DeleteDeviceCustomFieldSchema),
    },
  • src/index.ts:306-306 (registration)
    Handler map entry mapping 'delete_device_custom_field' string to the imported deleteDeviceCustomField function with schema validation.
    delete_device_custom_field: async (input) => deleteDeviceCustomField(DeleteDeviceCustomFieldSchema.parse(input)),
  • src/index.ts:20-20 (registration)
    Import of the schema from deleteDeviceCustomField.ts.
    DeleteDeviceCustomFieldSchema,
Behavior2/5

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

No annotations provided. Description only states it removes a definition, but does not disclose side effects (e.g., impact on existing devices), reversibility, or authorization requirements.

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?

Two concise sentences with no redundant information. Every sentence adds value.

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?

Adequate for a simple 1-param tool, but lacks details on permanence of deletion and effects on existing devices that reference this field.

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

Parameters4/5

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

Schema coverage is 100%. The description adds a warning to ensure the user wants to delete a device custom field and not an identity custom field, providing context beyond the schema.

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?

Description clearly states the action (delete) and resource (device custom field configuration/definition). It distinguishes from siblings like create_device_custom_field and delete_identity_custom_field.

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 versus alternatives (e.g., delete_identity_custom_field). No exclusion criteria or prerequisites mentioned.

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