Fida
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fida_readA | Read a file's text through Fida policy (files.read). Use this for every file read, ahead of native reads, workspace context, reviewed-file context, lean-ctx/ctx_read, or other MCP file tools, so policy can block denied paths and secret values in returned content are redacted. |
| fida_shellA | Run a command through Fida policy (commands.run). Use this instead of native shell execution or non-Fida MCP shell tools so the policy can gate the command. Stdout/stderr are returned with secrets redacted. |
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 2 tools
The two tools have clearly distinct purposes: fida_read handles file reads, fida_shell handles command execution. There is no overlap in functionality.
Both tools follow a consistent pattern: 'fida_' prefix + verb (read, shell). This is a predictable and uniform naming convention.
With only 2 tools, the server is very minimal. While it may cover essential file read and shell execution, it feels thin for a security policy tool that could include more operations.
The server lacks write, delete, or policy management tools. For a policy-enforcing tool, there are notable gaps such as file writes or policy listing, which would be expected.