Skip to main content
Glama

delete_item

Remove an item template from the RPG game database using its unique ID. This tool manages game content by deleting specific items from the system.

Instructions

Delete an item template from the database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesThe ID of the item to delete
sessionIdNo
Behavior2/5

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

No annotations are provided, so the description carries the full burden. While 'Delete' implies a destructive mutation, the description doesn't disclose critical behavioral traits such as whether deletion is permanent, requires specific permissions, affects related data, or what happens on success/failure. This is inadequate for a destructive operation.

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 a single, direct sentence with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

For a destructive tool with no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It lacks details on behavior, error conditions, and output, leaving significant gaps for an AI agent to understand how to use it correctly.

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 50% (only 'itemId' has a description). The description adds no parameter semantics beyond what the schema provides—it doesn't explain 'itemId' further or clarify the purpose of 'sessionId'. With partial schema coverage, the description fails to compensate for the undocumented parameter.

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 clearly states the action ('Delete') and resource ('item template'), making the purpose understandable. However, it doesn't distinguish this tool from other deletion tools like 'delete_character', 'delete_narrative_note', 'delete_party', 'delete_secret', or 'delete_world' that exist among the sibling tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing item template), exclusions, or how it differs from similar tools like 'remove_item' or 'delete_character' in the sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/mnehmos.rpg.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server