Skip to main content
Glama
Sign In
Backpack Battles MCP

Backpack Battles MCP

by 53721222-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

bpb_edit_items

Enter a mode to edit item positions while the backpack stays fixed, allowing items to be placed in any grid, including outside the bag—useful after purchases to arrange items in ideal spots.

Instructions

进入“只编辑物品”模式：背包固定不动，物品可以放到任意格子（包括包外）。用于购买后先把物品摆到理想位置。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It usefully states that the backpack stays fixed and items may be placed anywhere, including outside the bag. It does not explain how to exit the mode, whether other state changes occur, or what happens to existing placements.

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

Conciseness4/5

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

The description is two compact sentences with the mode behavior front-loaded. Every sentence contributes: the first defines the mode, the second gives the purchase-time use case. It could be slightly more structured for scanning but is not verbose.

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?

With zero parameters and no output schema, the description covers the core mode behavior and one use case. It is still incomplete for an agent choosing among several edit-mode tools because it omits mode exit behavior and explicit sibling differentiation. The missing context is material for invocation choice.

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?

The tool takes zero parameters, so there is no parameter semantics to explain. The schema has 100% description coverage and the description does not need to compensate for undocumented inputs. Baseline 4 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?

The description names a specific mode with a concrete verb phrase: entering 'edit items only' mode. It clarifies scope by saying the backpack is fixed while items can be placed in any grid, including outside the bag. It does not explicitly distinguish this from similarly named siblings such as bpb_open_item_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 Guidelines3/5

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

It provides one usage scenario: after purchasing, to place items in ideal positions first. However, it gives no when-not guidance and does not compare this tool with the many other edit-mode siblings. The usage is implied rather than explicitly scoped.

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