Project Content 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 |
|---|---|
| latest_project_dataC | Get latest project data including file names and contents |
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 confusion or overlap between tools. The single tool 'latest_project_data' has a clear and distinct purpose of retrieving project data, so disambiguation is perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'latest_project_data' follows a clear verb_noun pattern (get is implied in the description), and there are no other tools to cause inconsistency.
A single tool is generally too few for a server named 'Project Content Server', which suggests a scope that might include operations like creating, updating, or deleting project data. This minimal set feels thin and incomplete for the implied domain.
The server's name implies handling project content, but the tool only provides read access to latest data. There are significant gaps, such as no ability to create, update, delete, or manage project files, which will likely cause agent failures in typical workflows.