Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Gsettings Describe

gsettings_describe

Describe a gsettings key to show its allowed range and accepted values. Use it to verify valid settings before changing or hardening Linux desktop configurations.

Instructions

Describe a gsettings key and its allowed range/values.

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

Input Schema

NameRequiredDescriptionDefault
keyYes
schemaYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It correctly frames the operation as informational rather than mutating, but never states that it is read-only, what happens when the schema or key does not exist, or any permission requirements. For a simple query tool this is thin but not misleading.

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?

A single front-loaded sentence with no filler and no redundancy. The brevity is appropriate in form, though it edges toward under-specification rather than crispness.

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?

The existence of an output schema means return values need not be described, and the tool's core concept is conveyed. However, for a tool with two required, undescribed parameters and zero annotation coverage, the definition leaves the schema/key relationship and failure behavior unexplained.

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 needed to explain both parameters and does not. 'a gsettings key' loosely maps to the key parameter, but the required schema parameter — which namespaces the key — is never mentioned, leaving half the inputs to be guessed from the schema names alone.

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 gives a specific verb and resource ('Describe a gsettings key') plus the payload an agent cares about ('allowed range/values'), which implicitly distinguishes it from gsettings_get (which retrieves the current value). It stops short of naming any sibling explicitly, so the differentiator is inferred 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?

There is no explicit when-to-use or when-not-to-use statement and no mention of gsettings_get, gsettings_set, or the list tools. Usage is only implied: an agent can reason that describing a key precedes setting it, but that inference is left entirely to the caller.

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