Skip to main content
Glama

rebuild_indexes

Regenerate vanilla tuning, game Python, and TDESC indexes so Sims 4 modding agents can search resources and validate code accurately.

Instructions

(Re)build the vanilla tuning, game Python and TDESC indexes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rebuild_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
tdescNo
tuningNo
python_apiNo

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses the scope of what gets indexed, which is useful, but says nothing about whether existing indexes are overwritten or invalidated, whether the operation is long-running or safe to interrupt, or whether it must run before other index-dependent tools. For a mutation-style maintenance operation with zero annotation coverage, these are significant gaps.

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?

The single sentence is front-loaded with the action and wastes no words. Its brevity is efficient, though the terseness contributes directly to the gaps flagged in the other dimensions.

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?

With four undocumented parameters, no annotations, and no output schema, the description would need to do more work. Nothing is said about return value, success indication, or the effect of 'force', so an agent cannot call this confidently beyond accepting all defaults.

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% across four parameters. The description names the three index domains (tuning, Python, TDESC), which loosely maps to the tdesc/tuning/python_api flags, but adds no semantics such as defaults or what happens when a flag is false. The 'force' parameter is never mentioned or explained, leaving its most consequential behavior undocumented.

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 (build/rebuild) and names the concrete resources affected: vanilla tuning, game Python, and TDESC indexes. That is clearly distinct from siblings like read_vanilla_tuning or search_game_python_api, which read rather than index. It stops short of explicitly contrasting itself with any sibling, so a 4 rather than 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?

There is no statement of when this should be invoked — e.g., after a game patch, on first setup, or when searches return stale results — and no mention of prerequisites or cost. Usage is only implied by the word 'rebuild'. An agent must guess whether it needs this tool at all.

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