Skip to main content
Glama

read_vanilla_tuning

Returns the complete XML of an indexed vanilla tuning by instance ID, so you can inspect base-game tuning before overriding or extending it in a mod.

Instructions

Return the complete XML of an indexed vanilla tuning.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "read_vanilla_tuning"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations, so the description carries the full burden. 'Complete XML' usefully signals an untruncated single-document return rather than a summary, but nothing is said about permissions, behavior on an unknown instance_id, size limits, or mutation risk (implied read-only only by the verb).

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though its brevity edges toward under-specification rather than crisp completeness.

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?

For a simple single-parameter read tool this covers the core: what it returns (complete XML) and that it targets one indexed tuning. Missing are the origin of instance_id and error behavior, and with no output schema and no annotations the definition leaves those gaps entirely open.

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 the single required instance_id, so the description must compensate. 'Indexed vanilla tuning' hints that the id refers to an index entry, but it never says where such an id comes from (presumably search_vanilla_tuning) or what form it takes, leaving the parameter largely unexplained.

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?

Specific verb-plus-resource: 'Return the complete XML of an indexed vanilla tuning.' An agent knows this fetches full content for one tuning. It doesn't explicitly contrast with the sibling search_vanilla_tuning, so the read-vs-search distinction is only implied by the verb.

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?

No when-to-use statement, no prerequisites, and no mention of when to prefer this over search_vanilla_tuning or get_tuning_dependency_graph. The only guidance is the implicit 'indexed' qualifier, which an agent must infer means a valid instance_id is required.

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