Skip to main content
Glama
sanjibani

hawksoft-mcp

by sanjibani

create_log_note

Append a log note with optional follow-up task to a client's record. Use this to document phone calls, emails, summaries, or any interaction visible in HawkSoft.

Instructions

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. "Phone From Insured") or LogAction int. description: One-sentence summary shown in the activity feed. body: Full note text. May be multi-line. ref_id: Unique UUID for idempotency. Auto-generated if omitted. ts: ISO 8601 timestamp. Defaults to now (UTC). policy_id: Optional policy GUID to link the note to. policy_index: Optional 1-based index on the policy. action: Optional action code. task_title: Set to create a follow-up task. task_description: Task description. task_due_date: ISO 8601 due date. task_assigned_to_role: One of SpecifiedUser, Producer, CSR, Agent1, Agent2, Agent3. task_assigned_to_email: Required when assigned_to_role is SpecifiedUser. task_category: Optional category label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tsNo
bodyYes
actionNo
ref_idNo
channelYes
agency_idYes
client_idYes
policy_idNo
task_titleNo
descriptionYes
policy_indexNo
task_categoryNo
task_due_dateNo
task_descriptionNo
task_assigned_to_roleNo
task_assigned_to_emailNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It reveals that the tool appends a log note, can create follow-up tasks, and supports idempotency via ref_id. It does not detail auth requirements or failure modes, but provides sufficient behavioral context for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is moderately long but well-structured: purpose first, then usage guidance, then parameter list. The parameter list is in plain text but clear. Could be more structured (e.g., bullets), but not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters and 5 required, the description covers each parameter and provides usage context. Since an output schema exists, return values don't need explaining. Some behavioral details are missing but overall complete enough for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description includes an 'Args' section that explains all 16 parameters with context (e.g., 'Unique UUID for idempotency', 'Friendly channel name'). This fully compensates for the lack of schema descriptions, adding significant value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool appends a log note and optional follow-up task to a client record. It is explicit that this is the primary write tool for logging agent actions, distinguishing it from other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explicitly says 'call this whenever the agent does anything that should be visible in HawkSoft' and lists examples (phone call, email, etc.). However, it does not contrast with sibling tools like create_attachment, so some differentiation is missing. Strong guidance overall.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sanjibani/hawksoft-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server