Skip to main content
Glama

gc_dolphin_config_apply_profile

Apply a full Dolphin.ini profile to a specific emulator instance. Merges profile sections and keys into existing settings, overriding only specified values while preserving other keys.

Instructions

Apply a whole Dolphin.ini profile (a dict of section -> {key: value}).

This is Dolphin-only. Existing keys in the same section are preserved unless overridden by the profile.

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>",
      "profile": "<profile>"
    },
    "name": "gc_dolphin_config_apply_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the merge semantics ('Existing keys in the same section are preserved unless overridden'), but omits whether changes are persisted to disk, whether a restart or reload is required, what happens to sections absent from the profile, and what errors are raised on a malformed profile.

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?

Three short lines with the operation and its input shape front-loaded; nothing is redundant. The trailing newline-separated sentence on merge behavior is well placed rather than buried.

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 mutation tool with no annotations and no output schema, the definition covers the input shape and merge semantics but leaves persistence effects, failure modes, and the meaning of instance_id unexplained. An agent could call it but would not know the side effects or required emulator state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the profile parameter is a nested object, so the description's 'dict of section -> {key: value}' explanation is genuinely valuable. However, instance_id is never mentioned, and value types/constraints for the nested strings are not addressed.

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 and resource: 'Apply a whole Dolphin.ini profile', with the profile's shape spelled out as section -> {key: value}. The word 'whole' implicitly contrasts with the sibling gc_dolphin_config_set, but no sibling is named, so differentiation is left to inference.

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 line 'This is Dolphin-only' gives a scope constraint, but there is no explicit statement of when to prefer this over gc_dolphin_config_set or gc_dolphin_config_get, and no prerequisites (e.g., whether the emulator must be stopped). Usage is only implied.

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