Skip to main content
Glama

archive_account

Archive or unarchive a user account. Archiving removes the account from groups and unlinks subscriptions. Set archived=false to restore an archived account to active status. Requires finance:write scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>",
      "archived": "<archived>"
    },
    "name": "archive_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
archivedYestrue to archive the account, false to unarchive (restore to active status).
accountIdYesID of the account to archive or unarchive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / accountId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description carries the burden of disclosing consequences — and it does, stating that archiving removes the account from groups and unlinks subscriptions. It also names the required 'finance:write' scope, useful auth context not in the schema. It does not say whether the group/subscription unlinks are reversible on unarchive, which is the one material gap.

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?

Four short sentences, front-loaded with the operation, then consequences, then the reverse case, then the auth requirement. Nothing is redundant with the schema beyond a harmless restatement of the boolean.

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 two-parameter mutation with no output schema, the description covers the destructive side effects and the required scope, which is most of what an agent needs. The remaining omission is post-unarchive behavior for unlinked subscriptions and groups.

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% and the archived property already documents 'true to archive, false to unarchive'. The description's 'Set archived=false to restore' restates the schema rather than adding format or edge-case meaning, so the baseline 3 applies.

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 states a specific verb pair and resource ('Archive or unarchive a user account') and immediately enumerates the side effects (removal from groups, unlinking subscriptions), which implicitly separates it from delete_account and update_account. It stops short of naming those siblings explicitly, so an agent must infer the archive-vs-delete distinction.

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?

It clearly explains how to invoke the reverse operation ('Set archived=false to restore an archived account to active status'), which is genuine when-to-use guidance for the boolean. However, there is no guidance on when to archive versus delete an account, nor any stated prerequisites beyond the scope requirement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.