strateegia MCP Server
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 |
|---|---|
| list-projectsB | List projects from Strateegia API |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'list-projects' has a clear, singular purpose that cannot be confused with any other tool in the set.
The single tool name 'list-projects' follows a consistent verb_noun pattern (list + projects). With only one tool, there is no inconsistency or deviation in naming conventions to evaluate.
A single tool is generally too few for a server's purpose, as it severely limits functionality and suggests an incomplete or thin implementation. For a Strateegia API server, one tool does not provide adequate coverage for typical operations like creating, updating, or deleting projects, or managing other resources.
The tool set is severely incomplete for a Strateegia API server. With only a 'list-projects' tool, there are obvious gaps in CRUD operations (e.g., create, update, delete projects) and other essential functionalities like managing users, tasks, or reports, which are typical in project management domains.