Skip to main content
Glama
Sign In
sims4-tc-mcp

sims4-tc-mcp

by SomeoneToldJotaroDolphins-AreGood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

compile_tuning_with_simdata

Validate tuning XML and generate the matching 0x545AC67A SimData file so Sims 4 mod resources stay consistent and package-ready.

Instructions

Validate tuning XML and compile matching 0x545AC67A SimData.

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": {
      "xml_content": "<xml_content>",
      "output_dir": "<output_dir>"
    },
    "name": "compile_tuning_with_simdata"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_dirYes
xml_contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations whatsoever, the description carries the full behavioral burden and does not meet it. It does not say what happens on validation failure (exception, error list, partial compile), whether output_dir must pre-exist or is overwritten, or what artifacts land in the output directory. Only the target SimData type is disclosed.

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?

A single front-loaded sentence with no filler, but its brevity borders on under-specification rather than efficient concision. Nothing is wasted, yet there is very little to work with.

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

Completeness2/5

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

For a two-required-parameter mutation/compile tool with no annotations and no output schema, the definition omits failure semantics, output artifact expectations, and preconditions. The agent can guess the call shape but cannot predict the result.

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?

Schema description coverage is 0%, so the description must compensate for two undocumented parameters. It implies xml_content is tuning XML and that compiled SimData goes to output_dir, but says nothing about directory creation, overwrite behavior, file naming, or expected XML shape, leaving the required parameters underspecified.

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?

The description states two concrete verbs (validate, compile) and their resources (tuning XML, SimData), including the specific SimData instance type 0x545AC67A, which is meaningfully more specific than the tool name alone. It does not explicitly distinguish itself from neighbors like generate_runtime_tuning_hook or validate_and_build_ts4script, but the validate-then-compile pairing makes the operation identifiable.

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?

There is no statement of when to use this tool, when not to, or which sibling to pick instead (e.g., whether generate_runtime_tuning_hook is a follow-up step or an alternative path). The agent must infer usage from the name and description alone.

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