D&D 5e SRD Oracle

Query Character Session

query_character_session

Read-onlyIdempotent

Read one calculated result for a finalized D&D 5e character outside battle: ability checks, jump, proficiency, speed, AC, spells, forms, rituals, or weapon mastery, with no state change.

Instructions

Read one calculated result for a finalized character outside Battle without changing its state. Choose query.kind for ability-check abilities or jump abilities, proficiency, linked speeds, Armor Class, spell access, known forms, rituals, or Weapon Mastery, and supply only that variant's fields. The character must be available in this Play Session. Use inspect_character_session for stored character and core sheet facts, or apply_character_session_operation to change it.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Choose exactly one kind and provide its required fields. Returns a read-only projection; it does not roll checks, cast spells, spend resources, or change selections.
`characterId`	Yes	Character Session id from finalize_character or list_characters in this Play Session. The character must be available outside Battle.
`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.

Changed2 schema fields changedv0.1.1Sep 21, 2026

addedInput schema / properties / characterId / description

Added value: +"Character Session id from finalize_character or list_characters in this Play Session. The character must be available outside Battle."

addedInput schema / properties / query / description

Added value: +"Choose exactly one kind and provide its required fields. Returns a read-only projection; it does not roll checks, cast spells, spend resources, or change selections."

First observedSep 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, lowering the burden. The description reinforces this with 'without changing its state' and adds operational context: the character must be finalized, outside Battle, and available in the current Play Session. It does not contradict the annotations and adds modest context beyond them.

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?

Three dense sentences with no filler: purpose is front-loaded, the query-kind guidance is centralized, the prerequisite is stated, and alternative tools are named. Every sentence earns its place.

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?

For a complex polymorphic read tool, the description is complete: it covers what the tool reads, the precondition, the query-kind selection, and sibling routing. The detailed variant schemas and output schema carry the remaining specification, so nothing essential is missing.

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%, so the parameters are already well-documented. The description adds useful high-level guidance—'Choose query.kind' and 'supply only that variant's fields'—but this mostly restates the discriminated-union structure already expressed in the schema's required fields and additionalProperties constraints.

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: 'Read one calculated result for a finalized character outside Battle without changing its state.' It also enumerates the query domains and explicitly contrasts this tool with inspect_character_session and apply_character_session_operation, making sibling differentiation clear.

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?

It states the core use case—computed results for finalized characters outside Battle—and the prerequisite that the character must be available in the Play Session. It explicitly routes to inspect_character_session for stored/core sheet facts and apply_character_session_operation for mutations, leaving no ambiguity about alternatives.

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