Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

set_config_value

Set a configuration key to a specified value to modify system settings.

Instructions

Set config

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
valueYes

Implementation Reference

  • The actual implementation of set_config_value. Validates the key exists in config, updates the config object, saves to config.json file, and returns success/failure.
    function setConfigValue(key, value) {
      try {
        if (!(key in config)) {
          return {
            success: false,
            message: `Unknown configuration key: ${key}`
          };
        }
    
        config[key] = value;
    
        // Save to file
        fs.writeFileSync(configPath, JSON.stringify(config, null, 2));
    
        logger.info(`Configuration updated: ${key} = ${JSON.stringify(value)}`);
        return {
          success: true,
          message: `Configuration updated: ${key}`,
          [key]: value
        };
      } catch (error) {
        logger.error(`Error setting config value: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Input schema registration for set_config_value tool: requires 'key' (string) and 'value' (any).
    { name:'set_config_value', description:'Set config', inputSchema:{ type:'object', properties:{ key:{type:'string'}, value:{} }, required:['key','value'] } },
  • Handler dispatch: calls terminalTools.setConfigValue(args.key, args.value) when the tool name matches 'set_config_value'.
    case 'set_config_value': data = terminalTools.setConfigValue(args.key, args.value); break;
  • Test example generator: provides sample arguments { key: 'commandTimeout', value: 8000 } for set_config_value.
    case 'set_config_value': return { key:'commandTimeout', value: 8000 };
    case 'execute_command': return { command: process.platform==='win32' ? 'echo hello' : 'echo hello', waitForCompletion: true, shell: process.platform==='win32'? undefined : '/bin/sh' };
    case 'read_output': return { pid: 0 }; // replaced dynamically
    case 'force_terminate': return { pid: 0 }; // replaced dynamically
  • Imports terminalTools from '../tools/terminal_tools', which exports the setConfigValue function.
    const terminalTools = require('../tools/terminal_tools');
Behavior2/5

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

No annotations provided; description doesn't disclose if changes are persistent, require permissions, or have side effects. Minimal transparency for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short but not effective; under-specification harms usefulness. Every sentence should earn its place, but here there is only one vague phrase.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity, no output schema, and no annotations, the description is completely inadequate. Does not explain return values, failure modes, or usage context.

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

Parameters1/5

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

Schema coverage is 0% and description adds no meaning to the 'key' and 'value' parameters beyond their names. No hints about expected types or formats.

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

Purpose2/5

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

Description 'Set config' is a tautology of the tool name and lacks specificity. It fails to indicate which config or context, and does not differentiate from siblings like configure_effort_weighting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like get_config or show_algorithm_config. No context about prerequisites or scope.

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/FutureAtoms/agentic-control-framework'

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