D&D 5e SRD Oracle

Inspect Character Session

inspect_character_session

Read-onlyIdempotent

Inspect a stored character session to retrieve canonical HP, hit dice, spell slot, pact slot, and resource facts derived from the build.

Instructions

Inspect one selected Character Session as its canonical stored session plus core build-derived Hit Point, Hit Dice, Spell Slot, Pact Slot, and resource facts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`characterId`	Yes	Character Session id returned by finalize_character or list_characters.
`playSessionId`	Yes	Play Session handle returned by create_play_session for follow-up stateful calls in the same local process or authenticated account.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already disclose read-only, idempotent, non-destructive behavior. The description adds useful context by clarifying that the response contains the canonical stored session plus build-derived facts, rather than a live or purely computed view. No contradiction with annotations.

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?

The description is a single, dense sentence with no filler. It front-loads the verb and object and then enumerates the precise result fields, making it easy to parse quickly.

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

Completeness4/5

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

For a read-only inspection tool with full schema coverage, clear annotations, and an output schema, the description adequately conveys what the call returns. The only notable gap is the absence of usage context distinguishing it from similar session-related sibling tools.

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%, and both characterId and playSessionId have meaningful descriptions explaining where the values come from. The tool description itself adds no parameter-level detail, so the baseline of 3 applies.

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 clearly identifies the action ('Inspect'), the target ('one selected Character Session'), and the scope of the result (canonical stored session plus core build-derived HP, Hit Dice, Spell Slots, Pact Slots, and resource facts). It is specific but does not explicitly differentiate from the sibling query_character_session.

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 guidance is provided. It does not mention when to pick this over query_character_session, read_play_session, or other sibling session tools. The word 'selected' hints at prior selection but offers no actionable instruction.

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