mcp-flyin
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 |
|---|---|
| echoB | Echo back the input message |
| calculateC | Perform basic arithmetic calculations |
| get_system_infoC | Get basic system information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Package Configuration | The package.json file for this MCP server |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: calculate handles arithmetic, echo returns input, and get_system_info retrieves system data. An agent can easily differentiate between these three unrelated functions.
The naming is mostly consistent with a verb-based pattern (calculate, echo, get_system_info), though 'echo' is less descriptive than the others. There are no mixed conventions, making the set readable and predictable.
With only 3 tools, the server feels thin for a general utility purpose like 'mcp-flyin', which might imply broader functionality. While each tool is distinct, the count is borderline low for typical server scopes.
The toolset is severely incomplete for a utility server, lacking common operations like file handling, data transformation, or network requests. It covers only basic arithmetic, echoing, and system info, leaving significant gaps for agent workflows.