Skip to main content
Glama
Sign In
wyt-mcp

wyt-mcp

by MLMecham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

record_event

Log a scene by specifying text, witnesses (NPCs present), and an optional tone (cruel, despairing, kind) to record events for the dungeon RPG's memory.

Instructions

Log a scene that should be remembered. witnesses: npc keys who saw it. tone (optional): cruel | despairing | kind — this is the one place your judgment feeds the rules. Use it honestly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "record_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
toneNo
witnessesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the tool affects rules via the 'tone' parameter and implies a write operation. This is adequate, though it could mention more about side effects or reversibility.

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?

The description is two sentences: the first states purpose, the second details parameters and a usage note. Every sentence earns its place, with no wasted words.

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 the context (no output schema, no annotations, 3 parameters), the description covers all necessary aspects: what it does, parameters, and a usage principle. It is complete for an agent to understand and use the tool.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'witnesses' as NPC keys, and 'tone' with explicit values (cruel, despairing, kind). The 'text' parameter is implied as the scene content, adding meaning beyond the schema.

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: 'Log a scene that should be remembered.' This is a specific verb and resource, and the mention of 'judgment feeds the rules' distinguishes it from sibling tools like 'recap' which likely summarizes past events.

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

Usage Guidelines4/5

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

The description provides context for when to use the tool (logging memorable scenes) and includes a usage ethic ('Use it honestly'). However, it does not explicitly state when not to use it or compare directly to alternatives.

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