SapperMCP

Overview Schema Source Related Servers Discussions Admin

Gsettings List Schemas

gsettings_list_schemas

Lists installed GSettings schemas and filters results by substring, helping you find GNOME, desktop, or app schema keys before inspecting or changing settings.

Instructions

List installed gsettings schemas, optionally substring-filtered (e.g. 'gnome', 'zora', 'desktop').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsettings_list_schemas"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`filter`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.6/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 burden. It usefully discloses that filtering is substring-based (not exact match) and gives three example fragments, but says nothing about result ordering, truncation at the limit, or whether an empty result is an error.

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?

A single front-loaded sentence with inline parenthetical examples; every clause adds information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-value explanation is not required, and this is a simple read-only listing with zero required parameters. The only material gap is the unmentioned limit/truncation behavior, which matters for a schema catalog that can exceed 300 entries.

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 the description must compensate. It does add genuine meaning for 'filter' by stating it is a substring match with examples, which the bare schema does not convey. However, the 'limit' parameter (default 300) and its truncation behavior are never mentioned, leaving half the parameters undocumented anywhere.

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 ("List installed gsettings schemas") and clarifies the scope is the schema namespace, which implicitly separates it from gsettings_list_keys and gsettings_get. It does not explicitly name a sibling or state a boundary, 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?

Usage is only implied: an agent can infer it is the discovery step before fetching keys or values, and examples ('gnome', 'zora', 'desktop') hint at when to filter. There is no explicit statement of when to use this versus gsettings_describe or gsettings_list_keys, and no guidance on when to omit the filter.

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

Deploy Server