Skip to main content
Glama
Sign In
wyt-mcp

wyt-mcp

by MLMecham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

attack

Initiate combat with an NPC or raid a den. Choose auto mode for trivial enemies or manual round-by-round for dangerous foes.

Instructions

Start a fight. target: an npc key, or 'den_keeper' at a den to raid it. mode='auto' fast-forwards trash; dangerous foes refuse auto and demand round-by-round (combat_action).

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": {
      "target": "<target>"
    },
    "name": "attack"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoauto
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations provided; description discloses key behaviors: auto mode fast-forwards trash, dangerous foes refuse auto and require combat_action. However, does not detail outcomes or other effects like damage or success conditions.

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 concise sentences with front-loaded purpose. No extraneous words.

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?

Covers core usage and behavior; lacks return value specification but acceptable for a simple game action tool. Sibling and output schema not needed for completeness here.

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

Parameters5/5

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

Schema has 0% coverage; description fully explains both params: target value options and mode defaults/behaviors. Adds essential meaning beyond names and types.

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?

Clear verb 'Start a fight' and specific resource (target: npc key or den_keeper). Differentiates from sibling combat_action by explaining mode behavior.

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 when to use auto mode vs. combat_action for dangerous foes. Also clarifies target can be 'den_keeper' for raiding.

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