Skip to main content
Glama
Sign In
wyt-mcp

wyt-mcp

by MLMecham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rest

Recover health and resources by pausing at safe locations. The tavern offers reliable recovery while Tobias holds.

Instructions

Take what the place you're standing in has to give. The tavern is the only reliable one — while Tobias holds.

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": "rest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are present, and the description does not disclose any behavioral traits. It does not indicate whether the action is read-only, destructive, or safe. The agent has no information about side effects, permissions, or resource modifications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but not concise in a useful way. It uses ambiguous language and does not front-load key information. It appears more like flavor text than a functional description, wasting the limited space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the sibling tools (many actions like attack, look, buy), the description is completely inadequate. It does not help the agent distinguish when to use 'rest' versus other actions, and with no parameters or output schema, the agent has no context to make an informed decision.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and schema description coverage is 100% trivially. However, the description adds no meaning beyond the empty schema. It does not explain what the tool accomplishes, leaving the agent with no semantic context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Take what the place you're standing in has to give. The tavern is the only reliable one — while Tobias holds.' is vague and poetic. It does not clearly state that the tool is for resting or recovering. The name 'rest' provides some hint, but the description fails to specify the action or resource affected.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, prerequisites, or situations where 'rest' is appropriate or preferable to other sibling tools like 'buy' or 'use_item'.

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