Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

get_filesystem_status

Check filesystem status to monitor disk health and usage. Use a random string input to trigger the check.

Instructions

FS status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYes

Implementation Reference

  • The handler for 'get_filesystem_status' — directly returns an object with { success, readonlyMode, allowedDirectories }. No imported helper function is used; it's an inline case in the main MCP server's switch statement.
    case 'get_filesystem_status':
      data = { success:true, readonlyMode, allowedDirectories };
      break;
  • Registration of the tool's name, description, and inputSchema. It requires a dummy 'random_string' parameter with no real validation.
    { name:'get_filesystem_status', description:'FS status', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
  • The 'tools/list' response block where 'get_filesystem_status' is registered as one of the available tools.
    case 'tools/list':
      const tools = [
          { name:'setWorkspace', description:'Set workspace', inputSchema:{ type:'object', properties:{ workspacePath:{ type:'string' } }, required:['workspacePath'] } },
          { name:'initProject', description:'Init project', inputSchema:{ type:'object', properties:{ projectName:{type:'string'}, projectDescription:{type:'string'} } } },
          { name:'addTask', description:'Add task', inputSchema:{ type:'object', properties:{ title:{type:'string'}, description:{type:'string'}, priority:{type:'string'}, dependsOn:{type:'string'}, relatedFiles:{type:'string'} }, required:['title'] } },
          { name:'addSubtask', description:'Add subtask', inputSchema:{ type:'object', properties:{ parentId:{type:'number'}, title:{type:'string'} }, required:['parentId','title'] } },
          { name:'listTasks', description:'List tasks', inputSchema:{ type:'object', properties:{ status:{type:'string'}, format:{type:'string'} } } },
          { name:'updateStatus', description:'Update status', inputSchema:{ type:'object', properties:{ id:{type:'string'}, newStatus:{type:'string'}, message:{type:'string'} }, required:['id','newStatus'] } },
          { name:'getNextTask', description:'Next task', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
          { name:'updateTask', description:'Update task', inputSchema:{ type:'object', properties:{ id:{type:'string'}, title:{type:'string'}, description:{type:'string'}, priority:{type:'string'}, relatedFiles:{type:'string'}, message:{type:'string'} }, required:['id'] } },
          { name:'removeTask', description:'Remove task', inputSchema:{ type:'object', properties:{ id:{type:'string'} }, required:['id'] } },
          { name:'getContext', description:'Get context', inputSchema:{ type:'object', properties:{ id:{type:'string'} }, required:['id'] } },
          { name:'generateTaskFiles', description:'Generate task files', inputSchema:{ type:'object', properties:{} } },
          { name:'parsePrd', description:'Parse PRD', inputSchema:{ type:'object', properties:{ filePath:{type:'string'} }, required:['filePath'] } },
          { name:'expandTask', description:'Expand task', inputSchema:{ type:'object', properties:{ taskId:{type:'string'} }, required:['taskId'] } },
          { name:'reviseTasks', description:'Revise tasks', inputSchema:{ type:'object', properties:{ fromTaskId:{type:'string'}, prompt:{type:'string'} }, required:['fromTaskId','prompt'] } },
          // Filesystem
          { name:'read_file', description:'Read file', inputSchema:{ type:'object', properties:{ path:{type:'string'}, timeout:{type:'number'} }, required:['path'] } },
          { name:'read_multiple_files', description:'Read multiple files', inputSchema:{ type:'object', properties:{ paths:{ type:'array', items:{type:'string'} } }, required:['paths'] } },
          { name:'write_file', description:'Write file'+(readonlyMode?' (RO)':''), inputSchema:{ type:'object', properties:{ path:{type:'string'}, content:{type:'string'} }, required:['path','content'] } },
          { name:'copy_file', description:'Copy file'+(readonlyMode?' (RO)':''), inputSchema:{ type:'object', properties:{ source:{type:'string'}, destination:{type:'string'} }, required:['source','destination'] } },
          { name:'move_file', description:'Move file'+(readonlyMode?' (RO)':''), inputSchema:{ type:'object', properties:{ source:{type:'string'}, destination:{type:'string'} }, required:['source','destination'] } },
          { name:'delete_file', description:'Delete file'+(readonlyMode?' (RO)':''), inputSchema:{ type:'object', properties:{ path:{type:'string'}, recursive:{type:'boolean'} }, required:['path'] } },
          { name:'list_directory', description:'List directory', inputSchema:{ type:'object', properties:{ path:{type:'string'} }, required:['path'] } },
          { name:'create_directory', description:'Create directory'+(readonlyMode?' (RO)':''), inputSchema:{ type:'object', properties:{ path:{type:'string'} }, required:['path'] } },
          { name:'tree', description:'Directory tree', inputSchema:{ type:'object', properties:{ path:{type:'string'}, depth:{type:'number'}, follow_symlinks:{type:'boolean'} }, required:['path'] } },
          { name:'search_files', description:'Search files by pattern', inputSchema:{ type:'object', properties:{ path:{type:'string'}, pattern:{type:'string'} }, required:['path','pattern'] } },
          { name:'get_file_info', description:'File info', inputSchema:{ type:'object', properties:{ path:{type:'string'} }, required:['path'] } },
          { name:'list_allowed_directories', description:'List allowed dirs', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
          { name:'get_filesystem_status', description:'FS status', inputSchema:{ type:'object', properties:{ random_string:{type:'string'} }, required:['random_string'] } },
  • Test helper that generates a dummy argument { random_string:'x' } for the get_filesystem_status tool when generating MCP examples.
    case 'get_filesystem_status': return { random_string:'x' };
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., whether it is read-only, requires special permissions, or returns system state). The agent cannot infer safety or side effects.

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 brief, but this constitutes under-specification rather than conciseness. It lacks essential details that every sentence should provide.

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's apparent complexity (checking filesystem status), the description is completely inadequate. There is no output schema, and the description fails to cover what the tool returns or how it behaves.

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 description coverage is 0%, and the description does not explain the single required parameter 'random_string'. The parameter name is uninformative, and the description adds no meaning beyond the schema.

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?

Description 'FS status' is a tautology that merely restates the tool name without specifying any action or resource. It fails to distinguish from sibling tools like 'file_watcher_status'.

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 such as 'file_watcher_status' or 'get_file_info'. The description provides no context on appropriate use cases.

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