Skip to main content
Glama
Sign In
Backpack Battles MCP

Backpack Battles MCP

by 53721222-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

bpb_store_item

Moves an item from your backpack back to storage to free inventory slots for skills or new items; cannot be used on the backpack itself.

Instructions

把背包里的物品放回储物箱（腾出格子）。不能用于背包本体；用于给技能/新物品腾位置。

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": {
      "item_id": "<item_id>"
    },
    "name": "bpb_store_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes背包内物品 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations, so the description carries the burden; it does disclose that the operation mutates inventory state and that a slot is freed. It says nothing about whether the item can be retrieved from storage afterward, whether storage has a capacity limit, or what happens on failure — meaningful gaps for a write operation with zero annotation coverage.

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 with zero filler; the core action is front-loaded and the constraint plus motivation follow. Every clause earns its place.

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?

For a one-parameter mutation with no annotations and no output schema, the description covers purpose, exclusion, and motivation adequately. Remaining gaps (failure behavior, whether the storage target is implicit/singleton) are minor but real.

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% with a single parameter already described as '背包内物品 id'. The description's phrase '背包里的物品' reinforces that the id must be inside the backpack, but adds no syntax, range, or lookup guidance beyond the schema, so 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 specific verb+resource: move an item from the backpack back into the storage box, with the immediate effect (freeing a slot) named. The exclusion 'cannot be used on the backpack itself' further narrows the target. It does not explicitly contrast with the inverse sibling (bpb_place_item), so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives a concrete use case ('free a slot for a skill or new item') and an explicit when-not ('not for the backpack itself'). No alternative sibling is named, but for a single-purpose inverse-move tool the context is sufficient to select it.

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