Agentset
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTSET_API_KEY | Yes | Your Agentset API key | |
| AGENTSET_TENANT_ID | No | Optional tenant ID for the Agentset instance | |
| AGENTSET_NAMESPACE_ID | Yes | Your Agentset namespace ID |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| knowledge-base-retrieveA | Look up information in the Knowledge Base. Use this tool when you need to:
|
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
There is only one tool, so there is no possibility of confusion or overlap. The tool's purpose is clearly defined as knowledge base retrieval, making selection unambiguous.
With a single tool named knowledge-base-retrieve, there is no inconsistent naming pattern. The name is descriptive and predictable, though hyphenated rather than snake_case or camelCase.
One tool is borderline: it is sufficient for a simple read-only knowledge base retrieval service, but the 'Agentset' server name suggests a broader scope that is not reflected by a single tool.
The tool covers retrieval well, but there are no create, update, delete, or list operations. For a purely read-only knowledge base this may be sufficient, but for a general knowledge base or an agent set, the surface is incomplete.