Qualia MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUALIA_API_KEY | Yes | Your secret key for Qualia API | |
| QUALIA_USERNAME | Yes | Your organization ID for Qualia API |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify credentials work. If this fails, all other tools will too. |
| get_organizationA | Return the authenticated Qualia organization (id, name, display name). Use when: "what's my Qualia org id?" or "verify the org I'm authenticated as". Requires: organization:read capability gate. |
| list_ordersA | List title orders for the authenticated organization. Use when: "show me the last 10 orders" or "list orders awaiting closing". Args: limit: page size (default 25, max 100). offset: skip N orders for pagination. status: optional filter -- e.g. "OPEN", "CLOSED", "CANCELLED". Requires: orders:read capability gate. |
| get_orderA | Return a single title order by id (status, property address, timestamps). Use when: "look up order ORD-12345" or "what's the status of this closing?". Args: order_id: the Qualia order id (e.g. "ord_abc123"). Requires: orders:read capability gate. |
| list_messagesA | List messages on a title order (most recent first). Use when: "what's the latest message on this order?" or "show all messages from the buyer side". Args: order_id: the Qualia order id. limit: page size (default 25, max 100). Requires: messages:read capability gate. |
| send_messageA | Post a message on a title order. Use when: "send the buyer an update on the closing timeline" or "ask escrow to verify the wire instructions". Args: order_id: the Qualia order id. subject: short subject line (1-200 chars). body: message text (1-10000 chars). Plain text or basic markdown. Requires: messages:write capability gate. |
| list_documentsA | List documents attached to a title order (name, mime, size, created). Use when: "what documents are on this order?" or "did the buyer upload the LOI yet?". Args: order_id: the Qualia order id. limit: page size (default 25, max 100). Requires: documents:read capability gate. |
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 7 tools
Each tool has a clearly distinct purpose: order retrieval, organization info, health check, document listing, message listing, order listing, and message sending. No overlapping functionalities.
Most tools follow a verb_noun pattern (get_order, list_orders, send_message). 'health_check' is an exception but it's a common idiom. Overall consistent and predictable.
With 7 tools, the set is well-scoped for a title order management API. Each tool covers a necessary function without bloat or deficiency.
Covers essential read operations and message sending. Missing CRUD operations for orders (create, update) but the domain focus appears to be monitoring and communication, so minor gap.