Skip to main content
Glama

Give item

give_item

Adds a specified quantity of an item to an online Minecraft player's inventory by username; items that do not fit are lost.

Instructions

Add items to an online player's inventory. Items that do not fit are lost.

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": {
      "username": "<username>",
      "item": "<item>"
    },
    "name": "give_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesItem id such as 'minecraft:diamond' or 'bread'.
amountNoNumber of items (1-64).
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare a non-read, non-idempotent, non-destructive mutation, and the description adds a genuinely non-obvious consequence the annotations cannot convey: overflow items are permanently lost. It stops short of saying whether a partial failure occurs when only some items fit or what permissions/operator level are required.

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 short sentences, zero filler, with the operation stated first and the destructive side-effect caveat immediately after.

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?

With full schema descriptions, complete annotations, and an output schema, the definition covers what an agent needs to call it and warns about item loss. Only the permission model and partial-fit behavior are left open.

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%, so item ids, the 1-64 amount range, and the case-sensitive online username are all already documented in the schema. The description only restates 'items' and 'online player' without adding format or constraint detail, so the baseline 3 applies.

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?

States a concrete verb and resource: adding items to an online player's inventory. That clearly separates it from read siblings like get_inventory and from clear_inventory, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The phrase 'online player's inventory' implies the precondition (target must be online) and scope is implied by the verb, but there is no explicit when-to-use or when-not-to-use guidance and no routing to sibling tools.

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