sims4-tc-mcp

generate_runtime_tuning_hook

Generate Python 3.7 injection or stripping code for Sims 4 runtime tuning hooks, covering interactions, autonomy commodities, buffs, and super-affordance filters.

Instructions

Generate Python 3.7 injection/stripping code for runtime hooks.

hook_type: add_interaction | remove_interaction |
add_autonomy_commodity | start_buff | filter_super_affordances.

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": {
      "hook_type": "<hook_type>",
      "config_json": "<config_json>"
    },
    "name": "generate_runtime_tuning_hook"
  }
}

Input Schema

Name	Required	Description	Default
`hook_type`	Yes
`config_json`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the generated language and version (Python 3.7) and that code is both injected and stripped, but it never says whether the code is returned as text or written to a file, whether a build step is required, or what the call costs or mutates.

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?

Two compact blocks: a front-loaded purpose sentence, then the accepted values. Nothing is padded, though the trailing parameter listing reads as a dangling fragment without stating the field it belongs to or what config_json expects.

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?

With no annotations, no output schema, and 0% schema coverage, the description should say more about return value and config_json structure. It covers the hook_type domain adequately but leaves the second required parameter and the output shape undefined.

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% for both required parameters. The description enumerates the accepted hook_type strings, which adds real value beyond the enumless schema, but config_json — fully half the input — is never explained (no format, schema, or example), leaving a critical gap.

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 gives a specific verb and resource: 'Generate Python 3.7 injection/stripping code for runtime hooks,' and enumerates the hook_type values, so an agent knows what the tool produces. It does not differentiate this tool from siblings such as compile_tuning_with_simdata or get_tuning_dependency_graph, so it stops short of a 5.

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?

The listed hook_type values imply a scope, but there is no explicit statement of when to use this tool versus compile_tuning_with_simdata or the other tuning siblings, and no prerequisites or exclusions are given. Guidance is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server