Skip to main content
Glama
Sign In
Backpack Battles MCP

Backpack Battles MCP

by 53721222-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

bpb_open_backpack_edit

Enter backpack edit mode to move or rotate the backpack itself in Backpack Battles, enabling layout adjustments before combat or shop actions.

Instructions

进入背包层编辑模式（inventoryEditMode=bag），用于移动/旋转背包本体。

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_backpack_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the mode value (inventoryEditMode=bag) but does not state side effects, whether it exits another mode, prerequisites, or what the caller should expect afterward.

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 front-loaded sentence with no filler. It states the mode being entered and the practical purpose immediately.

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?

For a zero-parameter mode-entry tool with no output schema, the description gives the essential mode and purpose. However, without annotations it leaves out mode-transition behavior, exit conditions, and sibling differentiation, which an agent may need to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so parameter semantics are not a gap; the baseline is 4. The empty schema is consistent with a mode-entry action that takes no inputs.

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 specific action and target: entering backpack-layer edit mode (inventoryEditMode=bag) for moving/rotating the backpack body. The verb and resource are clear, but it does not distinguish this tool from close siblings such as bpb_edit_bags, bpb_set_edit_mode, or bpb_open_item_edit.

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 '用于移动/旋转背包本体' implies the tool's intended context, but there is no explicit when-to-use guidance relative to alternatives. An agent must infer whether this is preferable to bpb_edit_bags or bpb_set_edit_mode.

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