Skip to main content
Glama

Get a BattleBase account verification code

get_battlebase_link_code
Read-onlyIdempotent

Returns the code the player must put in their BattleBase profile tagline before importing games for this username. The player updates the tagline on BattleBase. Requires mcp:read.

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": {
      "username": "<username>"
    },
    "name": "get_battlebase_link_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes
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/5.0
Behavior4/5

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

Beyond the annotations, it adds the authentication requirement (mcp:read) and clarifies the external workflow: the player updates the tagline on BattleBase, not through this tool. It does not describe code lifetime, regeneration behavior, or failure cases, so it is not fully exhaustive.

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?

Three short sentences with no wasted wording. The core purpose and workflow are front-loaded, and the authentication constraint is stated plainly at the end.

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 simple read-only tool with rich annotations and no output schema, the description covers the purpose, required external action, and auth scope. It leaves minor gaps around code validity and error conditions, but those are not essential to invoking the tool correctly.

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 67%, and the two analytics parameters are already documented in the schema. The description adds only that the code is tied to 'this username'; it does not clarify whether that username is the BattleBase username or the platform username, nor does it explain username format beyond the schema pattern.

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 and resource: it returns the BattleBase verification code the player must place in their profile tagline before importing games for a given username. This is distinct from a simple account-link check, though it does not explicitly name the sibling tool it pairs with.

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?

It clearly states the context in which the tool is used: after the player updates their BattleBase tagline and before importing games for that username. It does not list exclusions or name an explicit alternative, which keeps it below 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