foundry-rest-api-mcp-server

Delete Foundry Entity

foundry_delete_entity

Destructive

Delete a Foundry entity permanently using its UUID or the current selection. This action cannot be undone.

Instructions

Permanently delete a Foundry entity by UUID or current selection. This action is irreversible.

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": "foundry_delete_entity"
  }
}

Input Schema

Name	Required	Description
`uuid`	No	Entity UUID
`userId`	No	Override the default userId. Omit for GM-level access.
`clientId`	No	Override the default clientId (which connected world to target)
`selected`	No	If true, delete the currently selected entity

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already flag destructiveHint: true, but the description adds valuable context by stating the deletion is 'Permanent' and 'irreversible.' It also discloses that the operation can target by UUID or current selection, going beyond the bare annotation to convey the action's finality and flexibility.

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 succinct sentences that front-load the action and key detail (UUID or selection). Every word earns its place; there is no redundant information or filler.

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?

The tool is straightforward, supported by full schema coverage and the destructiveHint/openWorldHint annotations. The description adds the critical fact of irreversibility. It doesn't delve into side effects like child deletions, but for a simple delete operation, the covered points are sufficient.

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 description coverage is 100%, so the baseline is 3. The description mentions 'by UUID or current selection,' which aligns with the uuid and selected parameters, but adds no further meaning beyond what the schema already documents. No additional insight is provided for userId or clientId overrides, so the baseline score stands.

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 the tool's function: 'Permanently delete a Foundry entity by UUID or current selection.' This specifies the verb (delete), resource (Foundry entity), and method (by UUID or selection), distinguishing it from sibling tools like create, update, and search.

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?

The description provides clear context for when to use the tool (when you want to delete an entity) and the two ways to target it (UUID or current selection). It does not explicitly cite alternatives, but the purpose is unmistakable given the tool name and sibling set, meeting the 'clear context, no exclusions' criterion.

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

Deploy Server