Skip to main content
Glama
moneyforward-i

Admina MCP Server

unmerge_identities

Reverse a previous merge of identity or people entities by providing IDs to separate them. Supports up to 50 people or identity IDs per request.

Instructions

Unmerge previously merged identity/people entities. Provide peopleIds, identityIds, or both to unmerge (up to 50 items each).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
peopleIdsNoList of people IDs to unmerge (1-50 items).
identityIdsNoList of identity IDs to unmerge (1-50 items).

Implementation Reference

  • The handler function that executes the unmerge identities tool logic. It takes peopleIds or identityIds, builds a request body, and calls POST /identity/unmerge API.
    export async function unmergeIdentities(params: UnmergeIdentitiesParams) {
      const client = getClient();
    
      const body: Record<string, unknown> = {};
      if (params.peopleIds !== undefined) body.peopleIds = params.peopleIds;
      if (params.identityIds !== undefined) body.identityIds = params.identityIds;
    
      return client.makePostApiCall("/identity/unmerge", new URLSearchParams(), body);
    }
  • Zod schema for validating input: peopleIds (array of positive ints, 1-50) and identityIds (array of strings, 1-50), both optional.
    export const UnmergeIdentitiesSchema = z.object({
      peopleIds: z
        .array(z.number().int().positive())
        .min(1)
        .max(50)
        .optional()
        .describe("List of people IDs to unmerge (1-50 items)."),
      identityIds: z.array(z.string()).min(1).max(50).optional().describe("List of identity IDs to unmerge (1-50 items)."),
    });
  • src/index.ts:242-247 (registration)
    Tool registration in the tools list with name 'unmerge_identities', description, and inputSchema.
    {
      name: "unmerge_identities",
      description:
        "Unmerge previously merged identity/people entities. Provide peopleIds, identityIds, or both to unmerge (up to 50 items each).",
      inputSchema: zodToJsonSchema(UnmergeIdentitiesSchema),
    },
  • src/index.ts:323-323 (registration)
    Handler registration mapping the 'unmerge_identities' tool name to the unmergeIdentities function with schema parsing.
    unmerge_identities: async (input) => unmergeIdentities(UnmergeIdentitiesSchema.parse(input)),
  • Re-export of the unmergeIdentities module from the tools barrel index.
    export * from "./unmergeIdentities.js";
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the basic action (unmerge) but does not mention if it is destructive, requires specific permissions, or has side effects. The description is clear but lacks depth.

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 is extremely concise, consisting of two sentences. The first sentence immediately states the purpose, and the second provides parameter usage. No unnecessary words.

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?

Given the tool has no output schema, the description does not explain what the result of unmerging is (e.g., updated identities or confirmation). It also omits potential prerequisites (e.g., entities must be merged). The description is partially complete but leaves gaps.

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% with descriptions for both parameters. The description adds value by clarifying that either or both parameter types can be provided, which is not explicitly stated in the schema. It also reinforces the item limits.

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 'unmerge' and the resource 'identity/people entities', distinguishing it from sibling tools like 'merge_identities'. The verb and resource are specific and unambiguous.

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

Usage Guidelines3/5

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

The description specifies that one can provide 'peopleIds', 'identityIds', or both, with a limit of 50 items each. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., when not to use it) and does not mention prerequisites like the entities must have been previously merged.

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