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 |
|---|---|
| listContentNamesC | List all content names from the organization's database optionally filtered by name |
| searchOrganizationContentsC | Search through the organization's content database using semantic search |
| deleteOrganizationContentC | Delete specific content from the organization's database |
| uploadContentFileAboutOrganizationC | Upload content file about the organization |
| uploadContentUrlAboutOrganizationC | Upload content url about the organization |
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 5 tools
Most tools have distinct purposes: listing, searching, deleting, and two upload methods (file vs. URL). However, 'listContentNames' and 'searchOrganizationContents' could be confused as both retrieve content, though 'search' implies semantic filtering while 'list' is name-based. The two upload tools are clearly differentiated by input type.
Naming is inconsistent with mixed conventions: 'deleteOrganizationContent' uses camelCase, while 'listContentNames', 'searchOrganizationContents', and the upload tools use a mix of camelCase and descriptive phrases. There's no uniform verb_noun pattern; for example, 'uploadContentFileAboutOrganization' is overly verbose and deviates from simpler naming like 'uploadContentFile'.
With 5 tools, the count is well-scoped for a content management server. It covers core operations (list, search, delete, upload via file, upload via URL) without being overwhelming or too sparse, fitting typical server purposes efficiently.
The toolset covers basic CRUD operations: create (via upload tools), read (list and search), and delete, but lacks an update tool for modifying existing content. This gap could cause agent failures if content needs editing, though agents might work around it by deleting and re-uploading.