Skip to main content
Glama

gc_dolphin_config_set

Set a single Dolphin.ini configuration value for a specific emulator instance by section and key. Use it to adjust per-instance Dolphin settings without editing the INI file manually.

Instructions

Set a single Dolphin.ini configuration value for an instance.

Writes to the instance's Config/Dolphin.ini. This is Dolphin-only.

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>",
      "section": "<section>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "gc_dolphin_config_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueYes
sectionYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real value by naming the persistence target (the instance's Config/Dolphin.ini) so the agent knows the change is durable on disk. It omits whether the write requires a restart, whether the value is validated against the section/key, and what happens on an invalid key.

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 short sentences, front-loaded with the action and target, and free of filler. The closing 'This is Dolphin-only' is mildly redundant given the tool name but still reads as an intentional scope guard.

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?

This is a mutation tool with no annotations, no output schema, and four undocumented parameters, so the description should carry more weight than it does. It never says what a successful write returns, whether the emulator reloads the setting, or how errors surface.

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 all four required parameters, so the description must compensate and does not: section, key, value, and instance_id are never explained or exemplified. The only hint is the implied section/key structure of an INI file, which is not enough to resolve semantics like value typing or instance identifier format.

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 names a specific verb (Set) and resource (a single Dolphin.ini configuration value) scoped to an instance, and 'single' plus 'Dolphin-only' implicitly separates it from the bulk gc_dolphin_config_apply_profile and from gc_dolphin_config_get. It stops short of explicitly naming those siblings, so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'single value' framing and 'This is Dolphin-only' scope note imply when to reach for this over a profile-based bulk operation, but no when-to-use or when-not-to-use rule is stated outright. There is no mention of prerequisites such as whether the instance must be stopped before writing.

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