Skip to main content
Glama
moneyforward-i

Admina MCP Server

archive_identity

Toggle the archive flag for an identity to manage its active state. Returns the updated identity with the new archive status.

Instructions

Toggle the archive flag for an identity. Returns the updated identity with the new archive state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identityIdYesThe ID of the identity to toggle the archive flag for

Implementation Reference

  • The handler function that executes the 'archive_identity' tool logic. It calls the Admina API PUT /identity/{identityId}/archive to toggle the archive flag.
    export async function archiveIdentity(params: ArchiveIdentityParams) {
      const client = getClient();
      return client.makePutApiCall(`/identity/${params.identityId}/archive`, {});
    }
  • Zod schema for the archive_identity tool input. Requires a single string field 'identityId'.
    export const ArchiveIdentitySchema = z.object({
      identityId: z.string().describe("The ID of the identity to toggle the archive flag for"),
    });
  • src/index.ts:261-264 (registration)
    Tool registration in the server's tool list with name 'archive_identity', description, and input schema.
    name: "archive_identity",
    description:
      "Toggle the archive flag for an identity. Returns the updated identity with the new archive state.",
    inputSchema: zodToJsonSchema(ArchiveIdentitySchema),
  • src/index.ts:326-326 (registration)
    Tool handler mapping in the toolHandlers record, linking 'archive_identity' name to the archiveIdentity function.
    archive_identity: async (input) => archiveIdentity(ArchiveIdentitySchema.parse(input)),
  • Re-exports archiveIdentity from src/tools/archiveIdentity.js via barrel export.
    export * from "./archiveIdentity.js";
    export * from "./unregisterIdentity.js";
Behavior3/5

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

With no annotations, the description carries full burden. It notes that the tool toggles the flag and returns the updated identity, indicating mutation. However, it lacks details on side effects, what archiving entails, or any restrictions beyond the basic action.

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 two concise, front-loaded sentences. The first states the action, the second mentions the return value. No unnecessary words or redundancy.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential behavior and return. However, it could benefit from explaining what archiving means conceptually, though it is mostly complete for basic use.

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 schema already describes identityId as 'The ID of the identity to toggle the archive flag for' (100% coverage). The description adds no additional meaning beyond repeating the toggle action, so baseline of 3 applies.

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 it toggles the archive flag for an identity, using the specific verb 'toggle' and resource 'identity'. It effectively distinguishes from sibling tools like update_identity or delete_identity by specifying a dedicated archive action.

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 vs alternatives such as update_identity or delete_identity. There is no mention of prerequisites or context for archiving, leaving the agent to infer usage independently.

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