Skip to main content
Glama

rest_party

Heals all party members and restores spell slots with a single command, replacing multiple individual rest calls to save tokens in RPG sessions.

Instructions

Rest entire party at once - heals all members and restores spell slots.

REPLACES: N×take_long_rest or N×take_short_rest (4-6 calls → 1 call) TOKEN SAVINGS: ~80%

Long rest (8 hours):

  • Restores ALL party members to max HP

  • Restores all spell slots

  • Clears concentration and active spells

  • Cannot rest while any member is in combat

Short rest (1 hour):

  • Rolls hit dice for healing (configurable per member)

  • Warlocks regain pact magic slots

  • Cannot rest while any member is in combat

Example - Long rest: { "partyId": "party-123", "restType": "long" }

Example - Short rest with hit dice: { "partyId": "party-123", "restType": "short", "hitDicePerMember": 2 }

Example - Short rest with custom allocation: { "partyId": "party-123", "restType": "short", "hitDiceAllocation": { "char-id-1": 3, "char-id-2": 1, "char-id-3": 0 } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partyIdYesThe party ID
restTypeYesType of rest to take
hitDicePerMemberNoHit dice each member spends on short rest (default: 1)
hitDiceAllocationNoCustom hit dice allocation per character ID (overrides hitDicePerMember)
sessionIdNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (healing, restoring spell slots, clearing effects), constraints (combat restriction), and different outcomes for long vs short rest. It doesn't cover error conditions or response format, but provides substantial behavioral context beyond basic functionality.

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 description is well-structured with clear sections: purpose statement, replacement context, long/short rest details, and examples. While comprehensive, every sentence serves a purpose - no wasted text. The examples are appropriately placed after the conceptual explanation.

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 mutation tool with no annotations and no output schema, the description provides substantial context: clear purpose, usage guidelines, behavioral details for both rest types, and parameter examples. It doesn't describe the return value format, but otherwise gives the agent sufficient information to understand when and how to use this tool effectively.

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?

The schema has 80% description coverage, establishing a baseline of 3. The description adds significant value through three detailed examples that illustrate parameter usage, show the relationship between hitDicePerMember and hitDiceAllocation, and demonstrate proper JSON structure. This goes well beyond what the schema descriptions provide.

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 clearly states the tool's purpose with specific verbs ('rest entire party', 'heals all members', 'restores spell slots') and distinguishes it from sibling tools by explicitly mentioning it replaces 'N×take_long_rest or N×take_short_rest'. This provides clear differentiation from the individual rest tools in the sibling list.

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?

The description provides explicit guidance on when to use this tool versus alternatives: it states it 'REPLACES: N×take_long_rest or N×take_rest' and quantifies token savings. It also specifies constraints like 'Cannot rest while any member is in combat' for both rest types, giving clear conditions for when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/mnehmos.rpg.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server