Skip to main content
Glama
Sign In
CalabiYau Map Engine MCP

CalabiYau Map Engine MCP

Official
by CalabiYauGames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_actors

Read-onlyIdempotent

Pages live actors by editor ID using browser session and revision pinning for consistent pagination during map inspection or editing.

Instructions

Page live actors using editor_id. Pin session and revision for consistent pagination.

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": {
      "browser_session_id": "<browser_session_id>"
    },
    "name": "list_actors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
item_idNo
selected_onlyNo
map_session_idNo
expected_revisionNo
browser_session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already cover read-only, idempotent, non-destructive behavior, and the description adds a meaningful pagination-consistency note. It still does not explain what 'live actors' means, what is returned, or what happens when session/revision are not pinned.

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?

The definition is two short sentences with the primary purpose front-loaded and little wasted text. The reference to 'editor_id' is a minor structural weakness because it does not map to any schema field.

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 seven-parameter list tool with no output schema and no parameter descriptions, the description is too sparse. It provides pagination guidance but does not explain filtering, selection, map/session scoping, or the shape of returned actor data.

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

Parameters2/5

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

With 0% schema description coverage across seven parameters, the description must do more work, but it only vaguely references 'session and revision' and mentions an 'editor_id' that is not a parameter. It leaves limit, offset, item_id, selected_only, map_session_id, and browser_session_id unexplained.

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 states a clear verb/resource pair: paging live actors. It distinguishes itself from list_items and list_sessions by naming actors specifically, though the reference to 'editor_id' is confusing because no such parameter exists in the schema.

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?

It gives useful pagination advice to pin session and revision for consistent pagination. However, it does not explicitly say when to use this tool versus list_items or get_state, so usage is only implied.

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

Deploy Server

Other Tools