Skip to main content
Glama
moneyforward-i

Admina MCP Server

unmerge_identities

Undo merges of people or identity entities by specifying their IDs. Provide up to 50 peopleIds or identityIds to separate combined records.

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 core handler function that executes the unmerge_identities tool logic. It sends a POST request to /identity/unmerge with peopleIds and/or identityIds.
    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 defining the 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-246 (registration)
    Registration of the 'unmerge_identities' tool with its name, 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 mapping that wires the 'unmerge_identities' tool name to the unmergeIdentities function with schema parsing.
    unmerge_identities: async (input) => unmergeIdentities(UnmergeIdentitiesSchema.parse(input)),
  • Imports getClient from admina-api.js which provides the HTTP client used to make the API call.
    import { getClient } from "../admina-api.js";
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the operation type (unmerge) and limits, but lacks detail on reversibility, permissions, or error handling. Adequate but not rich.

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?

Single sentence, concise and front-loaded with key information. No wasted words.

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

Completeness4/5

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

With two parameters and no output schema, the description covers the operation, parameters, and limits adequately. Lacks information on return values, but acceptable for a mutation tool.

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?

Input schema covers 100% of parameters with descriptions. Tool description adds that either list can be provided or both, marginally supplementing schema. 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?

Description clearly states the action ('unmerge') and the resource ('previously merged identity/people entities'), distinguishing it from its sibling 'merge_identities'.

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?

Explicitly says to provide peopleIds, identityIds, or both, with a limit of 50 items each. Provides clear context but no explicit when-not-to-use or alternative tools.

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