Skip to main content
Glama

game_get_entities

Read-only

List entities spawned by the bridge to inspect active game objects and support server- or player-level debugging.

Instructions

List entities spawned by the bridge

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

Input Schema

NameRequiredDescriptionDefault
playerNo
serverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds only the vague scoping phrase "spawned by the bridge" and says nothing about return format, pagination, ordering, or whether un-spawned entities are excluded — thin added value for a listing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler and the operation leads, which is good. But the brevity comes at the cost of under-specification rather than genuine compression — nothing is said about scope, results, or parameters.

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

Completeness2/5

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

For a two-parameter filtering/list tool with no output schema, the description should explain what entity fields come back and what the player/server filters do. Neither is covered, and with no output schema the return shape is entirely undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with two parameters (player as a bounded integer, server as a pattern-constrained string). The description never references either parameter, so their meaning, optionality implications, or filtering semantics must be guessed entirely from names and constraints.

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

Purpose3/5

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

"List entities spawned by the bridge" gives a verb (List) and a resource (entities), plus a scoping hint about the bridge. But "entities" is undefined, and nothing distinguishes this from siblings like game_get_state or game_get_entities vs. game_spawn, so the agent can't be sure what an entity is or how it differs from overall game state.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative is mentioned. An agent has no cue whether to call this versus game_get_state or game_screenshot, nor whether it requires a prior spawn — the description simply states the operation.

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