Headquarter
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
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 |
|---|---|
| list_projectsB | List all projects |
| get_projectC | Get a project by ID |
| create_projectC | Create a new project |
| update_projectC | Update an existing project |
| delete_projectB | Delete a project and all its issues |
| list_issuesB | List all issues, optionally filtered by project |
| get_issueA | Get an issue by ID |
| create_issueC | Create a new issue in a project |
| update_issueB | Update an existing issue |
| delete_issueB | Delete an issue |
| list_clientsB | List all clients |
| get_clientA | Get a client by ID |
| create_clientC | Create a new client |
| update_clientC | Update an existing client |
| delete_clientA | Delete a client and all their contacts |
| list_contactsC | List all contacts, optionally filtered by client |
| get_contactC | Get a contact by ID |
| create_contactC | Create a new contact for a client |
| update_contactC | Update an existing contact |
| delete_contactC | Delete a contact |
| list_notesA | List all notes |
| get_noteA | Get a note by ID |
| create_noteC | Create a new note |
| update_noteB | Update an existing note |
| delete_noteB | Delete a note |
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 25 tools
Every tool targets a distinct resource (client, contact, issue, note, project) with a unique action, making each tool's purpose clear and unambiguous.
All tool names follow a consistent verb_noun pattern (create_, delete_, get_, list_, update_) with the noun being the resource type, ensuring predictability.
25 tools is slightly high but appropriate for a domain covering five entities with full CRUD operations; each tool serves a distinct purpose and earns its place.
The tool surface provides full CRUD (create, read, update, delete, list) for clients, contacts, issues, notes, and projects, leaving no obvious gaps for basic lifecycle operations.