Skip to main content
Glama
Sign In
Backpack Battles MCP

Backpack Battles MCP

by 53721222-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

bpb_open_item_edit

Switches inventory to item edit mode, optionally focusing a specific item by ID, so you can make item-level changes in the running game.

Instructions

进入物品层编辑模式（inventoryEditMode=item）；可选 item_id 聚焦某件物品。

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

Input Schema

NameRequiredDescriptionDefault
item_idNo可选，要聚焦的物品 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It reveals that this changes an edit mode, but does not state whether the mode change has side effects, what prior state is required, whether it is reversible, or what the call returns.

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 compact sentence that front-loads the core action and then adds the optional parameter behavior. There is no redundant or wasted text.

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

Completeness3/5

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

It is minimally adequate for a mode-switching tool with one optional parameter and a fully described schema. However, with no annotations and no output schema, the description should do more to explain mode-transition behavior and how this differs from the edit-related sibling tools.

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 the item_id parameter is already documented in the schema. The description lightly reinforces its meaning by saying it focuses a specific item, but adds no format constraints or behavior beyond that baseline.

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 states a clear verb and resource: entering item-layer edit mode, with the concrete internal mode value inventoryEditMode=item. It is specific enough to understand the operation, but it does not explicitly distinguish itself from nearby siblings such as bpb_open_backpack_edit or bpb_set_edit_mode.

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?

It says to enter item edit mode and optionally focus an item, but gives no guidance on when to use this instead of bpb_open_backpack_edit, bpb_set_edit_mode, bpb_edit_items, or bpb_edit_all. Any prerequisites or mode-transition constraints are left 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