Skip to main content
Glama
rbilleci

bsh-mcp

by rbilleci

rest

Resolve a short or long rest declaration, applying campaign rules to determine if it succeeds and what resources are restored.

Instructions

Resolve a party's short- or long-rest declaration.

Call this for every rest declaration the party makes, short or long -- including a repeat later in the same session you expect to already be blocked. Whether a rest is available now depends on campaign state that moves between turns, so an earlier result or refusal in this conversation says nothing about this one: the tool's own response, never your memory of a previous answer, is what settles a rest. Restating an earlier answer without a fresh call states a mechanical fact no tool returned this turn -- the same failure as never calling at all.

The rest limits are the tool's to enforce, not yours to predict or pre-refuse: a declaration reaches this tool directly -- do not refuse it yourself or invent a confirmation step first -- and you narrate only what it returns, what was restored or why it refused.

character_ids names everyone resting. rest_type is short or long.

safe_environment matters only to a long rest and is trusted, never verified: the tool takes your word for the fiction. Set it true only when the party has actually secured a safe place -- a wilderness camp is not safe without a specific fictional reason. Setting it true unearned grants a durable recovery the fiction never earned, a worse defect than any refusal.

Whatever comes back, restored or refused, deliver it in fiction: the world answers the party, never a tool, a system, or an out-of-character aside.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
rest_typeYes
character_idsYes
safe_environmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses substantial behavior: the tool enforces rest limits itself, can refuse for campaign-state reasons, trusts safe_environment without verification, and grants durable recovery if safe_environment is set. It also warns against restating an earlier answer instead of making a fresh call.

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 longer than typical but organized into clear paragraphs and front-loaded with the core action. Some redundancy exists among 'do not refuse it yourself,' 'a declaration reaches this tool directly,' and 'deliver it in fiction,' but the length is largely earned given the subtle hallucination and safe-environment pitfalls.

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?

Given no annotations and no output schema, this is complete enough: it covers when to call, what each meaningful parameter does, how the tool behaves including refusal and trusted safe_environment, and how to translate results into fiction. An agent can invoke it correctly without additional context.

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 0% description coverage, so the prose must compensate. The description explains character_ids, rest_type, and safe_environment, including the long-rest-only and trusted semantics. However, it never explains the optional reason parameter, leaving one of four parameters undocumented.

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 opening line states a specific verb and resource: 'Resolve a party's short- or long-rest declaration.' It reinforces the scope by instructing to call it for every rest declaration, short or long, including repeats, which distinguishes it from the combat, character, and scene sibling tools.

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 gives explicit when-to-use guidance: call it for every rest declaration, and the tool's response is the only source of truth, not memory. It also gives exclusions: do not pre-refuse, do not add a confirmation step, and set safe_environment true only when the fiction has earned it.

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