VHGENGINE

by app.railway.up.engine-production-3bdc

delete_account

Destructive

Permanently delete this account. TERMINAL, not reversible. Admin scope (WP-LIFE). Pass confirm="delete" (guards accidents). Revokes ALL keys and deletes live profile facts/consent, hooks, webhooks, deliveries, jobs and idempotency; KEEPS bounded profile retraction markers, the immutable financial ledger, and de-associated outcome rows. Export FIRST with export_usage: ledger, every hook/immutable instance/outcome/profile, plus every retained job, commission and request tag in one call. Paged: get_usage/list_hooks/list_outcomes/list_jobs. Backup aging: GET /v1/legal. Errors: unauthorized, forbidden, invalid_request, rate_limited.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	API key for this call. Omit to fall back to the Authorization: Bearer / X-API-Key request header (streamable-HTTP only), then the VHGENGINE_API_KEY env var (the stdio default). No key resolvable -> unauthorized.
`confirm`	Yes	Must be exactly the string "delete". A guard: any other value (or omitting it) fails argument validation before anything is touched, so an accidental invocation cannot destroy the account.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Human-readable summary of what was and was not removed.
`deleted`	No	true once the account is tombstoned. Every key now 401s.
`retained`	No	{financial_events, anonymized_outcomes, creator_profile_retractions}: the ledger, de-associated outcome rows, and bounded profile exclusion markers survive. The outcome field keeps its legacy name; submitted content can remain.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description details exactly what is revoked/deleted (keys, profile facts, hooks, webhooks, deliveries, jobs, idempotency) and what is retained (retraction markers, ledger, outcome rows). It also emphasizes irreversibility ('TERMINAL, not reversible') and the confirm guard.

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 dense but every sentence provides essential information: terminal action, scope, guard, effects, retention, export first, pagination, and errors. It is front-loaded with the most critical words ('Permanently delete this account') and is well-structured despite its length.

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?

Given the tool's complexity and high stakes, the description covers all necessary context: what is destroyed, what is kept, how to prepare (export), how to list data, and error handling. It is fully complete for a destructive account-deletion tool, and the presence of an output schema further covers return values.

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 already provides complete, precise descriptions for both `api_key` and `confirm` (including the `const: "delete"` guard). The description only repeats the confirm requirement ('Pass confirm="delete"'), adding no new parameter-specific meaning beyond the schema, so it does not exceed the baseline.

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 opens with 'Permanently delete this account,' which uses a specific verb and resource, and is clearly distinct from sibling tools like delete_creator_profile and revoke_key. It also clarifies the scope ('Admin scope (WP-LIFE)') and the terminal nature of the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use it (admin scope) and includes a critical prerequisite: 'Export FIRST with export_usage.' It also provides alternative listing tools for paged access (get_usage/list_hooks/list_outcomes/list_jobs) and expected errors, guiding the agent on correct invocation and safety.

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

All VHGENGINE tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, e.g., signup vs. delete_account, create_key vs. revoke_key, generate_hooks vs. score_hook. Even similar tools like generate_hooks and generate_hooks_batch are clearly differentiated by single vs. batch operation.

Naming Consistency5/5

All 32 tools use a consistent verb_noun snake_case pattern (e.g., add_credits, create_checkout, revoke_key, list_outcomes) with no mixing of camelCase or other conventions.

Tool Count4/5

32 tools is slightly above the typical 15-tool range, but the domain is broad (account, keys, webhooks, generation, scoring, jobs, outcomes), and each tool has a specific purpose. No tools seem redundant.

Completeness4/5

The tool surface covers most lifecycle operations: CRUD for accounts/keys/webhooks, generation/scoring with batch and async variants, outcomes reporting, and auxiliary tools. Missing explicit delete for hooks (expire automatically) and some update operations, but no critical gaps.

Resources

Need Help?