Skip to main content
Glama
Sign In
wyt-mcp

wyt-mcp

by MLMecham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

advance_loop

Need to end the day? Send the player to bed with cause='slept', and the tool returns the overnight narrative of waking at the tavern. Death advances the loop on its own.

Instructions

End the day: the player goes to bed (cause='slept' — the only value you may pass; deaths advance the loop on their own). Returns the overnight packet to narrate waking up at the tavern.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "advance_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
causeNoslept

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that the tool returns 'the overnight packet to narrate waking up at the tavern'. While it lacks detail on packet contents, it gives sufficient behavioral context for a game narrative tool. No annotations are provided, so the description carries full burden.

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?

Two sentences, efficient and front-loaded with the core purpose. Every sentence adds value without redundancy.

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 simple tool with one parameter and no output schema, the description fully explains input, output, and usage context, leaving no gaps.

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 description explains the only valid value for 'cause' ('slept') and that it is the only allowed value, compensating for the 0% schema coverage. It adds meaning beyond the schema's default value.

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?

Clear verb 'End the day' and resource 'loop' (day-night cycle). However, does not explicitly differentiate from sibling tools like 'rest' or 'recap', though the context implies its unique role.

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?

Explicitly states 'cause='slept' — the only value you may pass' and notes that deaths advance the loop automatically, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools