Skip to main content
Glama

Show title

show_title

Display a large title and optional subtitle on a specific online Minecraft player's screen for a set duration.

Instructions

Show a big title and/or subtitle in the middle of an online player's screen.

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

Input Schema

NameRequiredDescriptionDefault
stayNoDuration in ticks (20 ticks = 1 second).
titleNoLarge title text.
fade_inNoDuration in ticks (20 ticks = 1 second).
fade_outNoDuration in ticks (20 ticks = 1 second).
subtitleNoSmaller text below the title.
usernameYesExact, case-sensitive name of an online player.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds only the placement detail ('middle of the screen') and says nothing about titles being transient, replacing an in-progress title, or the fade/stay timing behavior built into the parameters.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though it uses its brevity to skip behavior the agent would otherwise want.

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?

An output schema exists, so return values need not be described. For a six-parameter display tool, the description still omits the transient/overwrite nature of titles and any indication of how timing parameters interact, leaving a modest gap.

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 description coverage is 100%, with every parameter (including tick units, defaults, and the username pattern constraint) documented in the schema. The description adds no meaning beyond that, so the 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?

The description names a concrete action (display a title/subtitle) and the target (an online player's screen), so an agent can tell what the tool produces. It does not distinguish itself from display-oriented siblings such as broadcast_message, keeping it below 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 Guidelines3/5

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

The phrase 'online player's screen' implies the target must be online, which is a useful precondition. However, there is no explicit when-to-use versus alternatives (e.g., broadcast_message) and no statement of when not to use it; guidance is only implied.

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