Skip to main content
Glama
Sign In
wyt-mcp

wyt-mcp

by MLMecham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rapport

Judge whether a player's spoken line to an NPC is linguistically appropriate based on the NPC's manner, awarding or deducting rapport points and steadying the player when correct.

Instructions

Once per NPC per day: report whether the player genuinely spoke this NPC's language — judged against the packet's manner field, never your own taste. A well-aimed insult is a hit with Marta; flattery is a miss. 'Father' said sincerely is a hit with Bren; said smirking, a miss. hit=True is +1 (and steadies the player, once per day); hit=False is -1. Miss more than you hit — rapport is earned, not pleasant. Deeds still dwarf words.

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": {
      "npc_key": "<npc_key>",
      "hit": "<hit>",
      "why": "<why>"
    },
    "name": "rapport"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitYes
whyYes
npc_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: per-NPC daily limit, judgment based on manner field, point consequences of hit/miss, and the principle that deeds dwarf words.

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?

Description is concise and front-loads the key constraint. While it includes helpful examples, the structure is slightly rambling; could be more organized but not overly verbose.

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

Completeness3/5

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

Given no output schema, the description explains effects (point changes) but does not specify what the tool returns (e.g., a success message or the updated rapport value). Slightly incomplete for a mutation tool.

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

Parameters3/5

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

Schema coverage is 0%, so description must explain parameters. It provides examples for 'hit' and 'why' but does not fully define acceptable values or format for 'why', leaving some ambiguity.

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?

Description clearly states the tool reports whether the player genuinely spoke an NPC's language, judged by the packet's manner field. It distinguishes from sibling tools like 'talk_to' and 'npc_reward' by focusing on rapport evaluation.

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?

Provides implicit usage guidance: once per NPC per day, with examples of when a hit or miss occurs. However, it does not explicitly state when not to use or contrast with 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