Skip to main content
Glama

scene-get

Read-onlyIdempotent

Get full scene details: tokens (HP, AC, conditions, grid positions), walls, lights, notes, regions. includeMap (default true) appends an ASCII tactical map — walls, doors, numbered tokens with a legend — for spatial reasoning; false when you only need the lists. includeScreenshot=true adds a canvas screenshot (~100-500KB) for terrain, art and ambiance the map cannot convey — first view, not every turn. levels lists the scene's levels (Foundry 14+), weatherEffects the weather ids scene-set accepts (bridge module 8.19.0+). sceneId omitted = the active scene (scene-list has the IDs).

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": "scene-get"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsNoAppend the scene's levels (Foundry 14+)
sceneIdNoScene ID (omit for active scene)
includeMapNoAppend the ASCII tactical map (default true).
weatherEffectsNoAppend the weather effect ids for scene-set
includeScreenshotNoInclude canvas screenshot (~100-500KB). Recommended on first scene view or when visual context is needed. Skip during combat rounds to save context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / levels
      Added value: +{
      +  "description": "Append the scene's levels (Foundry 14+)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / weatherEffects
      Added value: +{
      +  "description": "Append the weather effect ids for scene-set",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent operation, and the description adds context beyond them that matters operationally: default payload behavior for includeMap, an approximate size cost (~100-500KB) and context-budget advice for screenshots, and version prerequisites (Foundry 14+ for levels, bridge 8.19.0+ for weatherEffects). This is exactly the kind of cost/feature gating an agent needs before invoking.

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?

It is front-loaded with the returned payload, then walks the parameters in a logical order with no filler sentences. The dense parenthetical clauses make it slightly harder to scan than it could be, but every clause carries functional information.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so thoroughly by enumerating the scene sections and what the ASCII map and screenshot contain. Combined with defaults, cost warnings, and version notes, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding cross-tool meaning the schema lacks — that weatherEffects yields IDs 'scene-set accepts' and that levels is tied to Foundry 14+. It largely restates the schema's default and size hints for includeMap/includeScreenshot rather than adding new semantics there.

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?

The description opens with a specific verb and resource ('Get full scene details') and enumerates exactly what is returned (tokens with HP/AC/conditions/positions, walls, lights, notes, regions). It also distinguishes itself from the sibling scene-list by noting 'scene-list has the IDs', so an agent can tell the two apart without inspecting schemas.

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?

Each optional switch comes with an explicit when-to-use rule: includeMap false 'when you only need the lists', includeScreenshot for 'first view, not every turn', sceneId omitted for the active scene. It names the alternative for ID lookup (scene-list) and the consumer of weatherEffects (scene-set), leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources