Skip to main content
Glama

Record that the person accepted the EULA

accept_eula
Idempotent

Records a person's confirmed Minecraft EULA acceptance for the active test server so Minecraft can start. Use only after showing them the EULA; never accept on their behalf.

Instructions

Writes eula=true for the active test server. Minecraft needs this to start. Only call it after you showed the person the Minecraft EULA (https://aka.ms/MinecraftEULA) and they said they accept it. Never accept it for them.

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": {
      "person_accepted": "<person_accepted>"
    },
    "name": "accept_eula"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_acceptedYestrue only if the person read the EULA and said they accept it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, idempotent, non-destructive write, and the description adds the crucial behavioral context: it writes eula=true for the active test server and is required for Minecraft to start. It also discloses the consent prerequisite and the prohibition against accepting for the user.

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 waste, front-loading the state change before the prerequisite and prohibition. Every sentence earns its place by adding a distinct operational constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter write tool with full schema coverage and annotations covering safety characteristics, the description supplies the remaining context an agent needs: target scope, effect, required prerequisite, and prohibition. No output schema is needed given the simple boolean state change.

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% and the single parameter is documented with a const value and explanation, so the schema carries the parameter meaning. The description reinforces the consent condition but adds no syntax or format details beyond what the schema already provides.

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 and resource: writes eula=true for the active test server. It also explains the consequence (Minecraft needs this to start), which distinguishes it from server lifecycle siblings like start_server.

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

Usage Guidelines5/5

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

Explicitly defines the precondition: only call after showing the person the Minecraft EULA and receiving acceptance, and never accept on their behalf. This is a clear when-to-use and when-not-to-use rule with no inference required.

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