Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

get_config

Retrieve configuration settings by providing a random string identifier.

Instructions

Get config

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYes

Implementation Reference

  • The getConfig function that executes the tool logic. It returns merged config with version info.
    /**
     * Get the current configuration
     */
    function getConfig() {
      try {
        return {
          success: true,
          ...config,
          version: require('../../package.json').version
        };
      } catch (error) {
        logger.error(`Error getting config: ${error.message}`);
        return {
          success: false,
          message: error.message
        };
      }
    }
  • Schema definition for the 'get_config' tool registration, requiring a dummy 'random_string' field.
    { name:'get_config', description:'Get config', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
  • Registration/handler dispatch: maps 'get_config' case to terminalTools.getConfig() call.
    case 'get_config': data = terminalTools.getConfig(); break;
  • The config object which getConfig() reads from (default shell, blocked commands, command timeout).
    let config = {
      defaultShell: process.env.DEFAULT_SHELL || (process.platform === 'win32' ? 'powershell.exe' : '/bin/bash'),
      blockedCommands: (process.env.BLOCKED_COMMANDS || '').split(',').filter(Boolean),
      commandTimeout: parseInt(process.env.COMMAND_TIMEOUT || '30000'),
    };
  • Export of getConfig from terminal_tools module.
    module.exports = {
      getConfig,
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to indicate any effects, required permissions, or side effects. A read operation is implied but not stated.

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?

The description is extremely short (two words), but this reflects under-specification rather than efficient communication. It is too minimal to be useful, wasting the opportunity to add value.

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 the tool has one parameter, no output schema, and no annotations, the description fails to provide essential context. It does not explain what 'config' refers to or what the return value looks like.

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?

The input schema has one required parameter 'random_string' with no description, and schema description coverage is 0%. The tool description does not explain the parameter's purpose or expected format, leaving the agent without guidance.

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

Purpose1/5

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

The description 'Get config' is a tautology that merely restates the tool name. It does not specify what configuration is being retrieved or distinguish it from siblings like set_config_value.

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?

The description provides no guidance on when to use this tool versus others (e.g., set_config_value). No context or alternatives are mentioned.

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