Daipendency
OfficialServer 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 |
|---|---|
| dependency_docs_getterC | Extract all the documentation and public API for a dependency of a local project |
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 has a single, clear purpose focused on extracting documentation and public API for a dependency.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'dependency_docs_getter' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Daipendency', which suggests a broader scope related to dependency management. This minimal toolset feels thin and incomplete for such a domain, lacking operations like listing dependencies, checking versions, or updating dependencies.
The tool surface is severely incomplete for dependency management. While the single tool extracts documentation, there are obvious gaps: no tools to list, add, remove, or update dependencies, check for vulnerabilities, or manage version conflicts. This limits agents to a narrow, read-only task.