Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Gsettings Set

gsettings_set

Set GNOME desktop configuration values by specifying a schema, key, and GVariant-formatted value, enabling precise system settings changes.

Instructions

Write a gsettings value. value uses GVariant syntax: true/false, 42, 'quoted-string', ['a','b'].

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": {
      "schema": "<schema>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "gsettings_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueYes
schemaYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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 at all, the description carries the full behavioral burden. It usefully discloses that value must be GVariant syntax with examples, which is the primary footgun of this tool. However, it omits whether writes persist to the dconf database, whether changes take effect immediately for running applications, and what happens on an invalid key or schema.

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 tight sentences with the action front-loaded and the syntax constraint immediately after. Nothing is wasted and the example literals are the highest-value information available.

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?

An output schema exists, so return values need not be explained. For a three-required-parameter mutation tool with no annotations and no schema descriptions, the definition is only partially sufficient: the critical value format is covered, but the schema/key pairing an agent must get right is left entirely implicit.

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%, so the description must compensate for all three parameters. It does address value well by specifying GVariant syntax and giving literals. But 'schema' and 'key' receive zero explanation, and 'schema' is genuinely ambiguous without knowing it means a GSettings schema ID such as org.gnome.desktop.interface.

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?

"Write a gsettings value" gives a specific verb and resource, and 'gsettings' clearly separates it from sibling families like dconf_* or set_clipboard. It does not explicitly contrast with gsettings_get, gsettings_reset, or dconf_write, but the write-vs-read/reset distinction is inferable from 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?

The description states what the tool does but gives no guidance on when to choose it over gsettings_reset (revert to default), dconf_write, or gsettings_describe (inspect a key first). There are no stated prerequisites, no mention that the key must exist in the schema, and no exclusions.

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

Deploy Server

Other Tools