tasksync-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_feedbackA | Read the contents of a feedback.md file (defaults to ./feedback.md). Before calling this tool you must seearch for the feedback.md file.If the feedback file does not exist, you will automatically create an empty feedback.md file before attempting to use this tool. During any process, task, or conversation, whether asking, replying, or completing phased tasks, you must call this tool to check for review. Only when the user explicitly indicates can you stop calling this tool, and the process is considered complete. MANDATORY USAGE RULES -PRIMARY DIRECTIVE:
|
| view_mediaA | Read an image file. Returns the base64 encoded data and MIME type. Only works within allowed directories. SUPPORTED FORMATS: Images: PNG, JPEG, GIF, WebP, BMP, SVG USAGE: Use this tool to read and encode image files for analysis, display, or processing. The tool streams files efficiently and returns base64-encoded data with proper MIME type detection. Args: path: Absolute or relative path to the image file within allowed directories |
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 serve entirely distinct purposes: get_feedback handles a continuous feedback loop for task management and user interaction, while view_media reads and encodes image files. There is no functional overlap or ambiguity between them, making tool selection clear and straightforward.
Both tools follow a verb_noun pattern (get_feedback, view_media), which is consistent and predictable. The naming is clear and descriptive, with only a minor deviation in that 'get' and 'view' are slightly different verbs, but they remain semantically appropriate and maintain overall coherence.
With only two tools, the server feels under-scoped for its implied domain of task synchronization and media handling. The get_feedback tool is heavily emphasized with extensive mandatory usage rules, suggesting a core focus, but the lack of complementary tools (e.g., for creating, updating, or managing tasks or feedback) makes the set appear incomplete and limited in functionality.
The server has significant gaps in coverage. While get_feedback provides a feedback mechanism and view_media handles image reading, there are no tools for core task management operations (e.g., create_task, list_tasks, update_task) or broader media manipulation. This incomplete surface will likely hinder agents in performing comprehensive workflows within the domain.