Skip to main content
Glama

settings_status

Read-only

Resolve managed, user, project, and local ThumbGate settings, revealing per-field origin metadata for clear policy visibility.

Instructions

Resolve managed, user, project, and local ThumbGate settings with per-field origin metadata for policy visibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the settings_status tool - a read-only tool with no inputs that resolves settings layers with origin metadata.
    readOnlyTool({
      name: 'settings_status',
      description: 'Resolve managed, user, project, and local ThumbGate settings with per-field origin metadata for policy visibility.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    }),
  • The main handler function that resolves settings hierarchy and returns active layers, origin summary, per-field origins, file paths, resolved settings, and warnings.
    function getSettingsStatus(options = {}) {
      const hierarchy = resolveSettingsHierarchy(options);
      return {
        activeLayers: hierarchy.activeLayers,
        originSummary: hierarchy.originSummary,
        origins: hierarchy.origins,
        paths: hierarchy.paths,
        resolvedSettings: hierarchy.resolvedSettings,
        warnings: hierarchy.warnings,
      };
    }
  • Core settings resolution logic: merges settings from defaults, managed, user, project, and local files in priority order, tracking the origin of each setting.
    function resolveSettingsHierarchy(options = {}) {
      const paths = resolveSettingsPaths(options);
      let settings = cloneValue(DEFAULT_SETTINGS);
      const originsByPath = Object.fromEntries(
        flattenLeafValues(DEFAULT_SETTINGS).map(([settingPath, value]) => [
          settingPath,
          {
            scope: 'defaults',
            sourcePath: null,
            value,
          },
        ]),
      );
    
      const activeLayers = [
        {
          scope: 'defaults',
          sourcePath: null,
          exists: true,
          leafCount: flattenLeafValues(DEFAULT_SETTINGS).length,
        },
      ];
    
      for (const scope of SETTINGS_SCOPE_ORDER.slice(1)) {
        const sourcePath = paths[scope];
        const data = readJsonObject(sourcePath);
        const exists = Boolean(data);
        activeLayers.push({
          scope,
          sourcePath,
          exists,
          leafCount: exists ? flattenLeafValues(data).length : 0,
        });
    
        if (!exists) {
          continue;
        }
    
        settings = mergeSettings(settings, data);
        for (const [settingPath, value] of flattenLeafValues(data)) {
          originsByPath[settingPath] = {
            scope,
            sourcePath,
            value,
          };
        }
      }
    
      const warnings = activeLayers
        .filter((layer) => !layer.exists && layer.scope !== 'defaults')
        .map((layer) => `No ${layer.scope} settings file at ${layer.sourcePath}`);
    
      return {
        resolvedSettings: settings,
        settings,
        originsByPath,
        origins: Object.entries(originsByPath)
          .sort((a, b) => a[0].localeCompare(b[0]))
          .map(([settingPath, origin]) => ({ path: settingPath, ...origin })),
        activeLayers,
        originSummary: summarizeOrigins(originsByPath),
        warnings,
        paths,
      };
    }
  • Helper that resolves the file paths for each settings layer (managed, user, project, local).
    function resolveSettingsPaths(options = {}) {
      const projectRoot = options.projectRoot || PROJECT_ROOT;
      const homeDir = options.homeDir || process.env.HOME || os.homedir();
    
      return {
        managed: path.join(projectRoot, 'config', 'thumbgate-settings.managed.json'),
        user: path.join(homeDir, '.thumbgate', 'settings.json'),
        project: path.join(projectRoot, '.thumbgate', 'settings.json'),
        local: path.join(projectRoot, '.thumbgate', 'settings.local.json'),
      };
    }
  • Registration in the MCP server dispatch - maps the 'settings_status' case to a call to getSettingsStatus() with no arguments.
    case 'settings_status':
      return toTextResult(getSettingsStatus());
Behavior4/5

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

Annotations confirm readOnlyHint=true; description adds that it returns per-field origin metadata, which is useful beyond the annotation.

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 sentence, front-loaded with verb 'Resolve', concise and no waste.

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?

Simple tool with no params and clear return info; slight lack of example or prerequisites but sufficient overall.

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?

No parameters, so baseline 4; description adds no extra param info because none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool resolves managed, user, project, and local settings with per-field origin metadata, which is specific and distinct from sibling tools.

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?

Implied usage for policy visibility, but no explicit guidance on when to use vs. alternatives like enforcement_matrix or get_branch_governance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IgorGanapolsky/ThumbGate'

If you have feedback or need assistance with the MCP directory API, please join our Discord server