get_session_summaryRetrieve aggregate stats for the current server session, including areas visited, deaths, level-ups, and last known area, from the local game log.
Return aggregate stats for the current server session: areas visited, deaths, level-ups, and last known area, derived from the local game log since this server started.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description adds context that the tool derives stats from the local game log and is scoped to the current server session. This goes beyond the annotation by explaining the data source and temporal scope, though it does not mention potential failures or resource limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence states the core purpose ('Return aggregate stats for the current server session') and lists the specific stats, with no redundant words. Every element earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, parameterless tool with no output schema, the description fully specifies what the agent can expect: the set of returned stats and their source (local game log since server start). Nothing necessary for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The schema is empty, and the description does not need to explain parameters. No additional parameter semantics are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns aggregate stats for the current session and lists specific metrics (areas visited, deaths, level-ups, last known area). It distinguishes from siblings like get_recent_events (event list) and get_current_area (current area only) by focusing on summary data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for session-level summaries but does not explicitly contrast with alternatives or state when not to use it. Given siblings like get_recent_events and get_current_area, the intended context is implied but not articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.