MCP Policy Gatekeeper
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_fileB | Create a new file (automatically applies snake_case naming convention) |
| read_fileC | Read contents of a file |
| write_fileB | Write to an existing file (naming convention enforced on creation only) |
| delete_fileC | Delete a file |
| list_filesC | List all files in directory |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| TalentX Workspace | Main protected directory managed by file-manager |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting specific file operations: create, delete, list, read, and write. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern (e.g., create_file, delete_file) using snake_case throughout. The naming is predictable and aligns perfectly with the operations performed.
With 5 tools, the server is well-scoped for file management, covering essential CRUD operations (create, read, update via write, delete) and listing. Each tool earns its place without being excessive or insufficient.
The tool set provides complete coverage for basic file operations in the domain, including create, read, update (write), delete, and list. There are no obvious gaps, and agents can perform full file lifecycle management without dead ends.