Skip to main content
Glama

Open the account deletion page

account_delete
Read-only

Opens the Portward account page in a browser so users can download their data or delete their account after signing in and confirming. No deletion happens automatically.

Instructions

Open the page where the user can download their Portward account data or delete their account, in their browser. It deletes nothing: the user signs in again there and confirms. Only call it when the user asks to download their account data, delete their account or leave Personal. History on this computer stays.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "account_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true; the description adds meaningful context that it 'deletes nothing' because the user re-authenticates and confirms on the page, and that local history is preserved. That is useful reassurance about the deferred destructive action, though it does not describe what the tool returns or what happens if the browser cannot open.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the main action and outcome, then the guard condition. The closing fragment 'History on this computer stays' is terse and slightly cryptic, and the placement of 'in their browser' after a clause boundary reads awkwardly.

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

Completeness5/5

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

For a zero-parameter page-opening tool with no output schema, all the information an agent needs to invoke it correctly is present: the action, the trigger conditions and the non-destructive behavior, and no annotation or schema gap remains unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema carries no semantic load and there is nothing for the description to disambiguate. The baseline of 4 applies; the description instead specifies what the call does on the user's behalf.

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?

States a specific verb and target ('Open the page where the user can download their Portward account data or delete their account, in their browser'), making the resource and outcome unambiguous. It is clearly distinguishable from session-control siblings like account_sign_in/account_sign_out because it only opens a browser page, and from a generic open_page because the destination is named.

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?

'Only call it when the user asks to download their account data, delete their account or leave Personal' gives explicit trigger conditions, a rarity. It stops short of naming a competing sibling (e.g. whether to use open_page for other destinations) or stating what to do if the user asks for related but different account actions.

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