Skip to main content
Glama
Sign In
worldanvil-mcp-server

worldanvil-mcp-server

by daireb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete article

delete_article

Permanently delete a World Anvil article using its UUID. Irreversible deletion with no trash bin, so verify the article ID before confirming.

Instructions

PERMANENTLY delete an article. This is irreversible — World Anvil has no trash bin for articles. Confirm with the user before deleting anything they didn't explicitly name.

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": {
      "article_id": "<article_id>"
    },
    "name": "delete_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYesUUID of the article to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does excellent work: discloses permanence, irreversibility, absence of a trash bin, and provides a user-safety confirmation directive. This goes beyond basic safety information.

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?

Two sentences, front-loaded with the critical warning, and zero unnecessary words. Every clause earns its place.

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 simple one-parameter destructive tool, the description covers the key context: irreversible deletion and user confirmation. No output schema is needed for a delete operation, and the warnings sufficiently prepare the agent.

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 clear description for article_id (UUID), so baseline 3 applies. The tool description adds no extra parameter meaning, which is acceptable given the schema already documents it fully.

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 the exact action (delete) and resource (article), emphasizes permanent deletion, and clearly distinguishes it from create/update/read siblings like update_article or get_article.

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?

Implies usage for article removal and explicitly instructs user confirmation for non-explicit deletions. However, it does not contrast with other tools or mention alternatives, leaving when-to-use vs siblings implicit.

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

Deploy Server

Other Tools