Skip to main content
Glama
Backpack Battles MCP

Backpack Battles MCP

by 53721222-gif

bpb_health

Verifies the in-game bridge is online and returns ping with a status summary to confirm the game is reachable before actions.

Instructions

检查游戏内网桥是否在线,返回 ping 与当前状态摘要。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose the return payload (ping and a current-status summary) and implies a non-mutating probe, but it says nothing about failure behavior, timeout/latency characteristics, or what the status summary contains.

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?

A single front-loaded sentence that states both the action and the return value with zero filler. Nothing could be removed without losing information.

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 zero-parameter liveness probe with no annotations and no output schema, the description covers what is checked and roughly what comes back. A short note on failure output (e.g., what an offline result looks like) would make it fully self-sufficient.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema's additionalProperties:false and empty property set are consistent with the parameterless description.

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 verb (检查/check) and a specific resource (游戏内网桥/in-game bridge) plus its liveness question, so an agent knows exactly what it does. It is distinguishable from state-reading siblings like bpb_get_state or bpb_get_phase because it targets bridge connectivity rather than game state, though it never says so 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?

Usage is only implied by the purpose — a health/ping check is naturally called to verify connectivity or after a failure. There is no explicit statement of when to prefer it over bpb_get_state, nor any guidance on retry/backoff or when calling it is unnecessary.

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