Skip to main content
Glama

list_settings

Lists stored settings records a caller is authorized to read, grouped by layer and key, and excludes host-only deployment entries from remote access.

Instructions

Return every stored settings record the caller may read, by layer and key.

A remote caller must be allowed config:read on the whole store (decided on an empty resource), and each record is then kept only if the caller may read its own layer. The host-only deployment layer is never returned to a remote caller.

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": "list_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A3.6/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, and it does disclose real behavior: the empty-resource permission check, per-layer post-filtering, and the exclusion of the host-only deployment layer from remote results. It does not describe ordering, pagination, or what an empty result looks like, and it never states that the tool is read-only, leaving that to inference from the verb.

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?

The description is front-loaded: the return scope appears in sentence one, with permissions and filtering as follow-up detail. Every sentence adds distinct information, though the parenthetical about deciding on an empty resource is dense and could be phrased more plainly.

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?

For a zero-parameter list tool with no annotations and no output schema, the description supplies the access-control and host-layer-exclusion facts an agent most needs before calling it. The omission of a return shape or ordering is a minor gap, since records are described as keyed by layer and key.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the 4 baseline applies; there is no parameter semantics to explain. The description wisely spends its words on the authorization and filtering context that the empty schema cannot convey.

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 first sentence gives a specific verb and resource ('Return every stored settings record ... by layer and key') plus the access scope ('the caller may read'), so the agent knows this is an enumerate-everything read rather than a single-value lookup. It never names its closest siblings (get_settings, get_effective_config), so the list-vs-get distinction is left implicit.

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 implied by the phrase 'every stored settings record' and by the required config:read permission, which tells the agent the call will fail without store-wide read rights. There is no explicit guidance on when to prefer this over get_settings or get_effective_config, and no statement of when not to call it.

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