Skip to main content
Glama
moneyforward-i

Admina MCP Server

unregister_identity

Toggles the management type of an identity to or from unregistered, updating the identity's status and returning the new management type.

Instructions

Toggle the unregistered management type for an identity. Returns the updated identity with the new management type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityIdYesThe ID of the identity to toggle the unregistered management type for

Implementation Reference

  • The handler function that executes the tool logic. It calls the Admina API to toggle the unregistered management type for an identity.
    export async function unregisterIdentity(params: UnregisterIdentityParams) {
      const client = getClient();
      return client.makePutApiCall(`/identity/${params.identityId}/unregister`, {});
    }
  • Zod schema defining the input: identityId (string).
    export const UnregisterIdentitySchema = z.object({
      identityId: z.string().describe("The ID of the identity to toggle the unregistered management type for"),
    });
  • src/index.ts:266-271 (registration)
    Tool registration in the server, mapping the name 'unregister_identity' to its description and schema.
    {
      name: "unregister_identity",
      description:
        "Toggle the unregistered management type for an identity. Returns the updated identity with the new management type.",
      inputSchema: zodToJsonSchema(UnregisterIdentitySchema),
    },
  • src/index.ts:327-327 (registration)
    Handler mapping: the 'unregister_identity' tool call delegates to unregisterIdentity() with parsed input.
    unregister_identity: async (input) => unregisterIdentity(UnregisterIdentitySchema.parse(input)),
  • Re-export of the unregisterIdentity module from the tools barrel file.
    export * from "./unregisterIdentity.js";
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It indicates the tool modifies state ('toggle') and returns the updated identity, but omits details about reversibility, permission requirements, side effects, or what 'unregistered management type' entails.

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 short sentences. Every word is functional with no unnecessary elaboration. It front-loads the action and states the return value efficiently.

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?

For a simple, single-parameter toggle tool without an output schema, the description covers the essential purpose and return value. It could be improved by explaining the concept of 'unregistered management type' or how the returned identity reflects the change, but it is largely adequate.

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 fully describes the only parameter (identityId). The description does not add any additional semantic value beyond what the schema already provides (parameter purpose is clear from schema description).

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 ('Toggle the unregistered management type') and the resource ('an identity'), with a specific verb. It distinguishes this tool from siblings like 'check_identity_management_type' or 'update_identity' by focusing on toggling the unregistered type.

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 is provided on when to use this tool versus alternatives such as 'update_identity' or 'check_identity_management_type'. The description lacks context on prerequisites or appropriate scenarios.

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