Skip to main content
Glama
Sign In
SapperMCP

SapperMCP

by MasterX1582
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dconf List

dconf_list

Lists keys and subdirectories under a specified dconf path ending in '/', helping inspect GNOME configuration directories and locate settings.

Instructions

List keys/subdirs under a dconf path (must end with '/').

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": {
      "path": "<path>"
    },
    "name": "dconf_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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?

With no annotations, the description carries the full behavioral burden; 'List' implies a read-only operation, and the trailing-slash precondition is disclosed. It does not say whether listing is recursive or immediate-children only, nor how missing or unreadable paths are handled. The existence of an output schema covers the return shape, limiting the gap.

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?

One front-loaded sentence with no filler, and the constraint is placed immediately after the purpose. It is terse to the point of being a fragment, but nothing is redundant.

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 one-parameter read tool with an output schema, the description covers purpose and the key input constraint. It stops short of the details that matter for correct invocation — path format examples and recursion semantics — leaving the agent to discover them by trial.

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 coverage is 0% for the single 'path' parameter, so the description must compensate and only partially does: it mandates a trailing slash but never shows a dconf path format (e.g. /org/gnome/desktop/interface/) or states whether absolute paths are required. An agent still has to guess the accepted path syntax.

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 ('List') and resource ('keys/subdirs under a dconf path'), which is enough to distinguish it from siblings like dconf_read and dconf_write that operate on values. It doesn't explicitly name those siblings, but the noun 'keys/subdirs' versus reading a value is a meaningful distinction.

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 parenthetical '(must end with "/")' gives a concrete precondition for calling it, and 'keys/subdirs' implies enumeration rather than value retrieval. However, there is no explicit guidance on when to choose this over dconf_read or the gsettings_list_* siblings, and no statement about what happens for a non-existent path.

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