Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

list_allowed_directories

Retrieve the list of directories that are permitted for access within the Agentic Control Framework.

Instructions

List allowed dirs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYes

Implementation Reference

  • Core implementation of listAllowedDirectories - returns the list of allowed directories as a success object. This is the actual function that executes the tool logic when 'list_allowed_directories' is called.
    function listAllowedDirectories(allowedDirectories) {
      return {
        success: true,
        message: 'Allowed directories listed successfully',
        directories: allowedDirectories
      };
    }
  • Tool registration/definition for 'list_allowed_directories' in the MCP server's tool list. Defines its name, description ('List allowed dirs'), and input schema (requires random_string).
    { name:'list_allowed_directories', description:'List allowed dirs', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
  • Handler dispatch in the MCP server's main switch statement. Routes 'list_allowed_directories' requests to filesystemTools.listAllowedDirectories(allowedDirectories).
    case 'list_allowed_directories':
      data = filesystemTools.listAllowedDirectories(allowedDirectories);
      break;
  • Testing utility that provides example arguments (random_string:'x') for generating MCP examples for the list_allowed_directories tool.
    case 'list_allowed_directories': return { random_string:'x' };
  • Input schema definition: type 'object', properties: random_string (type: string, required). Note: the handler doesn't use random_string from args, it only returns the allowedDirectories array.
    { name:'list_allowed_directories', description:'List allowed dirs', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It only states a read operation but gives no detail about side effects, permissions, or return format. The parameter 'random_string' is unexplained.

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?

Three words is extremely concise but at the cost of essential information. Under-specification masquerades as conciseness.

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?

With no output schema, no annotations, and a meaningless parameter, the description provides almost no useful information for an agent to correctly invoke the tool.

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 the description does not mention the sole parameter 'random_string', leaving its purpose entirely unclear.

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

Purpose3/5

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

The description 'List allowed dirs' indicates a listing operation but the term 'allowed' is ambiguous and does not distinguish from sibling 'list_directory'. It is vague but not a tautology.

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

Usage Guidelines2/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 siblings like 'list_directory' or what 'allowed' means. No context or exclusions provided.

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