Skip to main content
Glama
moneyforward-i

Admina MCP Server

unregister_identity

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

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 unregister_identity tool logic. It takes an identityId parameter and makes a PUT API call to /identity/{identityId}/unregister.
    export async function unregisterIdentity(params: UnregisterIdentityParams) {
      const client = getClient();
      return client.makePutApiCall(`/identity/${params.identityId}/unregister`, {});
    }
  • Zod schema for the unregister_identity tool input. Validates the identityId string parameter.
    export const UnregisterIdentitySchema = z.object({
      identityId: z.string().describe("The ID of the identity to toggle the unregistered management type for"),
    });
  • src/index.ts:267-271 (registration)
    Registration of the unregister_identity tool in the MCP server, defining its name, description, and input 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)
    Tool handler registration mapping the 'unregister_identity' tool name to its implementation function with schema-based input parsing.
    unregister_identity: async (input) => unregisterIdentity(UnregisterIdentitySchema.parse(input)),
  • Import of the UnregisterIdentitySchema from the tools module.
    UnregisterIdentitySchema,
Behavior2/5

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

No annotations are provided. The description indicates this is a mutation (toggles) but does not disclose side effects, required permissions, or potential risks. For a tool that changes state, more transparency is needed.

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 short sentences that convey the action and return value. There is no unnecessary information, making it concise and easy to parse.

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

Completeness2/5

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

Given the absence of annotations and output schema, the description is too brief. It lacks details on the return type, possible errors, the meaning of 'unregistered management type', and how it relates to other management types. More context is needed for proper tool selection.

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?

Schema coverage is 100% with a description for 'identityId'. The tool description adds the context of 'toggling the unregistered management type', which aligns with the parameter but does not provide additional semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies the action ('Toggle the unregistered management type') and the resource ('identity'), and mentions the return value. It is clear enough to distinguish from siblings like 'update_identity' which may change other attributes, but the meaning of 'unregistered management type' is not explained.

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'. There is no mention of prerequisites, context, or when to avoid using it.

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