Skip to main content
Glama

gc_dolphin_config_get

Retrieves a single Dolphin.ini configuration value from a Dolphin emulator instance using its section and key, so you can inspect emulator settings.

Instructions

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

This is Dolphin-only (real hardware has no such config).

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

Input Schema

NameRequiredDescriptionDefault
keyYes
sectionYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden; it does disclose that this is a non-destructive read scoped to Dolphin-backed instances and that real hardware has no equivalent config. It does not say what happens if the section/key is absent, whether the instance must be running, or what form the value takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the applicability caveat immediately after. Nothing is wasted or 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 simple three-parameter getter with no output schema and no annotations, the description covers the essentials of what it does, but leaves the return value's shape and the missing-key/error behavior unspecified. A little more detail would make it self-sufficient.

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 description coverage is 0%, so all three parameters rely on bare titles. The mention of "Dolphin.ini" and "for an instance" conveys that instance_id selects the emulator and that section/key map onto INI structure, which adds some meaning, but the expected string formats (instance id syntax, section names) remain 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?

States a specific verb ("Read") and resource ("a single Dolphin.ini configuration value for an instance"), which is unambiguous about what is returned. It does not explicitly name or disambiguate from the sibling gc_dolphin_config_set, 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 Guidelines3/5

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

The phrase "Read ... a value" implies this is the retrieval counterpart to the set/apply_profile siblings, and "Dolphin-only (real hardware has no such config)" gives a useful applicability boundary. However, it never explicitly says to use gc_dolphin_config_set to change values or states prerequisites such as the emulator being active.

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