agentic_actions_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bashC | This function will execute a bash command and return the output. This function is useful for executing bash commands including creating files, directories, and other bash commands. |
| python_codeB | This function will execute a python code and return the output. |
| python_fileB | This function will execute a python file and return the output. |
| globB | This function will return a list of files that match the given pattern. This function is useful for finding files in a directory. |
| grepB | This function will search for the given pattern in the specified file and return the matching lines. |
| read_fileB | This function will read the contents of a file and return it as a string. |
| write_fileA | This function will write the given content to a file. If the file does not exist, it will be created. |
| create_folderB | This function will create a folder with the given name. If the folder already exists, it will return a message indicating that the folder already exists. |
| delete_folderA | This function will delete a folder with the given name. If the folder does not exist, it will return a message indicating that the folder does not exist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct purpose: python_code, bash, and python_file are clearly separated by execution type; glob and grep handle search; read_file and write_file handle file I/O; create_folder and delete_folder handle directory operations. The descriptions make these boundaries explicit, so an agent can reliably disambiguate.
The tool names mix conventions: some are bare commands (bash, glob, grep), some are noun phrases (python_code, python_file), and some follow a verb_noun pattern (read_file, write_file, create_folder, delete_folder). While all use lowercase with underscores, the inconsistency in structure makes the set less predictable.
The server has 9 tools, which is a well-scoped size for a development utility. Each tool covers a separate need—execution, search, reading/writing files, and folder management—without unnecessary overlap or bloat.
The toolset provides execution, search, read/write, and folder lifecycle operations, but it lacks a delete_file tool. This is a notable gap: users can create and modify files but cannot remove them, which creates a dead end for file management workflows.