MCP Minecraft Remote

by nacal

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

tossItem

Throws items from your inventory. Specify item name and amount to discard selected items.

Instructions

Throw items from inventory

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": {
      "itemName": "<itemName>"
    },
    "name": "tossItem"
  }
}

Input Schema

Name	Required	Description	Default
`itemName`	Yes	Name of the item to throw
`amount`	No	Amount of items to throw

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.4/5.0

Behavior1/5

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

No annotations exist, and the description fails to disclose key behaviors: whether items are permanently lost, if any permissions are needed, or what the result of the action is. The description 'Throw items from inventory' implies removal but lacks essential details.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it is under-specified for a tool with no annotations or output schema. It should include more context to be useful.

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

Completeness1/5

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

Given no output schema and no annotations, the description should explain the consequences of the action (e.g., items are discarded). It fails to do so, leaving the agent without crucial context for a mutation tool.

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%, meaning the parameter descriptions already explain itemName and amount. The description adds no additional meaning beyond what the schema provides, warranting a baseline score of 3.

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 uses a specific verb 'Throw' and resource 'items from inventory', clearly indicating the action. However, it does not differentiate from sibling tools like depositItem or withdrawItem, which are also inventory manipulation actions.

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?

No guidance is provided on when to use this tool versus alternatives such as depositItem or withdrawItem. The agent is left to infer context from the name alone.

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