cognitive-tools-mcp / gikendaasowin-aabajichiganan
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 |
|---|---|
| deliberateD | – |
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 single tool 'deliberate' stands alone with no other tools to confuse it with.
A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'deliberate' follows a clear verb pattern, but consistency is trivially achieved with only one element.
A single tool is generally too few for most server purposes, as it limits functionality and suggests an incomplete or trivial scope. Without a description for 'deliberate', it's unclear if this minimal set is justified, but typically one tool feels thin and inadequate for meaningful agent interactions.
With only one tool and no description provided, it is impossible to assess coverage of any domain. The surface is severely incomplete, as no operations or lifecycle can be inferred, and agents will likely face dead ends due to the lack of actionable tools.