Squidbrake
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inbox_listA | List support emails in the shared inbox (newest first) with a short preview. |
| inbox_readB | Read one support email in full and mark it as read. |
| email_sendC | Send an email from support@acme.com. |
| crm_find_customerC | Find customers by email, name or company. |
| crm_add_noteC | Add a note to a customer's CRM record. |
| crm_update_planB | Change a customer's plan (free, starter, pro, team) or cancel it (cancelled). |
| payments_list_chargesC | List a customer's card charges, with any refunds already made. |
| payments_refundC | Refund all or part of a card charge back to the customer. |
| payments_transferC | Send a bank transfer (wire) from Acme's account. |
| acme_check_approvalB | Finish a acme call Squidbrake was holding for human approval (WAITING FOR HUMAN APPROVAL): runs it if approved, reports if rejected, or keeps waiting a little longer. |
| acme_recent_decisionsA | What people decided about your earlier requests (approved / rejected, by whom, and their notes). Check it before retrying something, and follow the notes. |
| acme_ask_userA | Ask a person on your team a question and wait for their answer, instead of guessing (which environment, which customer, is this safe). They answer in Squidbrake's dashboard or on their phone. If the answer isn't there yet, call this again with the event_id you were given. |
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 12 tools
Each tool maps to a distinct resource and action: inbox, CRM, payments, and human-in-the-loop functions are cleanly separated by prefix and description. The three acme_* tools are related but clearly differentiated (ask a question, check approval of a held action, review past decisions), so an agent should select correctly.
All names use snake_case with resource prefixes (inbox_, email_, crm_, payments_, acme_), which is largely predictable. Minor inconsistencies exist: email_send breaks the inbox_ email grouping, and acme_recent_decisions is noun-based rather than verb_noun.
12 tools is well within the ideal range and matches the breadth of the support-ops domain without bloat. Each tool appears to earn its place by covering a distinct capability.
Core support workflows—reading/replying to emails, looking up customers, updating plans, issuing refunds/transfers, and human escalation—are covered. Gaps include no email search/archive, no customer creation or general contact update, and no charge creation, but these are minor for the stated support context.