Skip to main content
Glama

settings_get

Retrieve all Unflick settings or read one specific key to inspect configuration values. Omit the key to get the full settings set.

Instructions

Read all settings, or a single key if provided

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

Input Schema

NameRequiredDescriptionDefault
keyNoOptional key name; omit to read all settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. "Read" does signal a non-mutating operation, but nothing is said about the return shape, whether values may include sensitive data, or what happens when the key does not exist.

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?

One short sentences that front-loads the verb and covers both branches with zero filler. Nothing could be removed without losing scope information.

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-optional-parameter read tool with no output schema, the core behavior is conveyed. The gaps that matter, namely the return value type and missing-key behavior, are not addressed, but the surface area is small enough that the omission is tolerable.

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 coverage is 100% and the single optional parameter is already documented as "Optional key name; omit to read all settings". The description restates that same omit-for-all semantics, adding no new meaning, so the baseline 3 applies.

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 pairs a specific verb ("Read") with a specific resource ("settings") and states both scopes: all settings or one key. The read framing implicitly separates it from settings_set/settings_unset, though no sibling is named explicitly.

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?

It states the two usage modes (omit key for all, supply key for one) and the schema repeats the same condition, so an agent can act without guessing. There is no explicit guidance on when to prefer this over settings_path or how to modify values after reading, leaving alternatives to inference.

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