ft_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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_timeA | Get the current system time in ISO 8601 format |
| calculate_file_hashA | Calculate the hash of a file using the specified algorithm |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_review | Review source code for potential issues and suggest improvements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project README | A sample read-only resource |
TDQS
Scored across 2 tools
The two tools, file hashing and system time, are in completely different domains with no overlap, making them easily distinguishable.
Both tools follow a clear verb_noun pattern with snake_case, providing a consistent naming convention.
With only two unrelated tools, the server feels thin and lacks a cohesive purpose; a more focused set would be appropriate.
Each domain has only a single tool, missing common operations (e.g., different hash algorithms or time zone variants), resulting in an incomplete surface.