Skip to main content
Glama

Enable or disable entity AI

set_entity_ai
Idempotent

Enable or disable a living mob's AI by UUID to freeze it in place or restore normal behavior.

Instructions

Turn a mob's AI on or off (living entities only).

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": {
      "uuid": "<uuid>",
      "enabled": "<enabled>"
    },
    "name": "set_entity_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesEntity UUID, e.g. as returned by summon_entity or get_players.
enabledYesFalse freezes the mob like a statue; true restores its AI.

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=true and destructiveHint=false, so the safety profile is covered. The description adds the living-entity scope constraint, which is genuine behavioral context, but it does not say what happens when a non-living or non-existent UUID is supplied, nor whether toggling affects in-progress actions.

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 the core action first and the scope qualifier second; no wasted words. It is arguably too terse for the information it carries, but nothing is redundant.

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?

With an output schema present and full parameter documentation, most of the agent's needs are met elsewhere. The remaining gap is edge-case behavior for invalid or non-living targets and whether players are excluded by 'living entities', which the description leaves unaddressed.

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%, including the meaningful detail that false freezes the mob like a statue, so the schema does the heavy lifting and baseline 3 applies. The description adds only the implicit constraint that the uuid must reference a living entity; no format or semantics beyond the schema.

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?

States a specific verb and resource ('Turn a mob's AI on or off') with an explicit scope restriction ('living entities only'). It is unambiguous what the tool does, though it doesn't differentiate itself from any sibling by name (e.g. set_entity_attribute, set_entity_target), so it stops short of the top band.

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 parenthetical 'living entities only' is a constraint that implicitly tells the agent when the tool applies, but there is no explicit when-to-use, when-not, or pointer to an alternative for non-living entities. The agent can infer the boundary but must do the reasoning itself.

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