Skip to main content
Glama

Import finished games from BattleBase

import_battlebase_history
Destructive

Imports up to 20 public games at a time from a verified BattleBase account, skipping unfinished or already imported games. Use a username when linking a new account after the player adds their verification code to their tagline. Confirm the import first, then repeat with nextCursor as before until nextCursor is null. Retrying the same page is safe. Requires mcp:manage.

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

Input Schema

NameRequiredDescriptionDefault
beforeNoThe nextCursor from an earlier import call. Omit on the first call.
usernameNo
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare write/destructive and open-world behavior, and the description adds real context beyond them: batch size cap of 20, skipping of unfinished and already-imported games, retry safety, and the mcp:manage permission requirement. It stops short of saying what exactly is created or what the response body 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?

Five tight sentences, front-loaded with the scope and batch limit, then the linking case, then the pagination loop. No filler or restatement of the title.

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?

With no output schema, the description still covers the loop-termination signal (nextCursor null), idempotent retry, and the auth scope, which is what an agent needs to drive it correctly. It leaves the return payload's shape and the confirmation step's mechanics implicit.

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?

Schema coverage is 75% and the description covers the one gap: 'username' is explained as the linking-a-new-account case, and 'before' is explained as the nextCursor loop mechanism with the null termination condition. It adds meaning beyond the schema for the two functionally important parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb + resource + scope: 'Imports up to 20 public games at a time from a verified BattleBase account.' The 'games' resource and the skipping rules make it clearly distinct from sibling importers such as import_collection and import_roster without needing to name them.

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 concrete procedural context: use 'username' when linking a new account after the verification code is added to the tagline, confirm the import, then loop with nextCursor until it is null. It does not explicitly contrast with the other import tools, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources