hawksoft-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HAWKSOFT_PASSWORD | Yes | HawkSoft Partner API password | |
| HAWKSOFT_USERNAME | Yes | HawkSoft Partner API username |
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 |
|---|---|
| list_agenciesA | List agency IDs that have subscribed to your HawkSoft vendor app. Returns an array of integer agency IDs. Each represents an independent insurance agency that has opted in to data sharing with your app via the HawkSoft License Management Portal. |
| list_officesB | List offices configured under an agency. Args: agency_id: HawkSoft agency ID (from list_agencies). |
| list_changed_clientsA | List client IDs that changed since a given timestamp. The workhorse for syncing. Pass an Args:
agency_id: HawkSoft agency ID.
as_of: ISO 8601 timestamp (e.g. |
| get_clientA | Fetch full details for a single client. Returns the full client object — details, people, contacts, claims, policies
by default. Use Args: agency_id: HawkSoft agency ID. client_id: HawkSoft client number. include: Sections to include: details, people, contacts, claims, policies, invoices. |
| get_clients_bulkA | Fetch multiple clients in one call (up to 200 per request). Args: agency_id: HawkSoft agency ID. client_numbers: List of client numbers (1–200 per call). |
| search_client_by_policyA | Find a client by exact policy number match. Useful when an agent has a policy number from a carrier but not the HawkSoft client number. Returns all clients (usually 1) holding that policy. Exact match only — no partial or fuzzy search. Args: agency_id: HawkSoft agency ID. policy_number: Exact policy number. include: Sections to include. |
| create_log_noteA | Append a log note (and optional follow-up task) to a client's record. The single most useful write tool — call this whenever the agent does anything that should be visible in HawkSoft: a phone call, an email, a conversation summary, a carrier touch. Args:
agency_id: HawkSoft agency ID.
client_id: HawkSoft client number.
channel: Friendly channel name (e.g. |
| create_attachmentA | Attach a base64-encoded file (PDF, image, doc) to a client record. Args:
agency_id: HawkSoft agency ID.
client_id: HawkSoft client number.
channel: Channel name or LogAction int (use list_channels for the catalog).
desc: One-line description of the file.
log_note: Log note text tied to this attachment.
file_name: File name including extension, e.g. |
| create_receiptsA | Record one or more payments received by a client. Each receipt applies to one or more invoices. A log note is automatically created and linked. Optionally create a follow-up task. Args:
agency_id: HawkSoft agency ID.
client_id: HawkSoft client number.
receipts: List of receipts. Each item must include:
- |
| list_channels_toolA | Return all 56 HawkSoft channel codes with friendly names and categories. Use this to discover the right |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| channels_resource | All HawkSoft LogAction channel codes — useful reference for the agent. Each entry has the integer value, the friendly label, and the channel category (Phone / Mail / Email / etc). |
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action: create_attachment, create_log_note, create_receipts for different logging operations; get_client and get_clients_bulk for client retrieval (single vs. bulk); list_agencies, list_channels_tool, list_offices for different listings; search_client_by_policy for policy-based search; and list_changed_clients for sync. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_log_note, get_client, list_agencies). The only minor deviation is list_channels_tool which appends '_tool', but it is still readable and clearly indicates its purpose.
With 10 tools, the set is well-scoped for a HawkSoft server covering client retrieval, logging activities (notes, attachments, receipts), and listing utilities (agencies, offices, channels, changed clients). Each tool earns its place without being excessive or sparse.
The core workflows are covered: retrieving clients (single, bulk, by policy), adding log notes, attachments, and receipts, and listing supporting entities. Minor gaps exist, such as no update or delete operations for logs or client data, but agents can likely accomplish typical tasks without dead ends.