Skip to main content
Glama
sanjibani

hawksoft-mcp

by sanjibani

create_attachment

Attach base64-encoded files (PDF, image, doc) to a HawkSoft client record and optionally create a follow-up task.

Instructions

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. "declaration_page.pdf". file_b64: Base64-encoded file contents — NO data: URL prefix. policy_id: Optional policy GUID to link to. ref_id: Idempotency UUID (auto-generated if omitted). ts: ISO 8601 timestamp (defaults to now). task_title, task_description, task_due_date, task_assigned_to_role, task_assigned_to_email, task_category: Optional follow-up task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tsNo
descYes
ref_idNo
channelYes
file_b64Yes
log_noteYes
agency_idYes
client_idYes
file_nameYes
policy_idNo
task_titleNo
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, so description carries full burden. Discloses important behavioral details: file_b64 must not have 'data:' URL prefix; ref_id is optional and auto-generated; lists all optional task-related fields. Could mention idempotency behavior or side effects, but overall effective.

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

Conciseness5/5

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

Starts with a one-sentence purpose, then uses a clear 'Args:' list format. Each parameter is explained concisely. No extraneous text.

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?

Covers all 16 parameters with meaningful descriptions. Output schema exists, so return values are not needed. Lacks file size limits or accepted MIME types, but overall complete for an attachment creation tool.

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%; the description provides explicit purpose for each of the 16 parameters (e.g., 'channel: Channel name or LogAction int ...', 'file_b64: Base64-encoded file contents — NO data: URL prefix'). This fully compensates for missing schema descriptions.

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?

Clearly states the action ('attach'), input type ('base64-encoded file'), allowed file types ('PDF, image, doc'), and target ('client record'). Distinguishes from sibling tools like create_log_note and create_receipts by focusing on file attachment.

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

Usage Guidelines3/5

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

Does not explicitly state when to use this tool versus alternatives. The purpose is implied (when attaching a file), but no 'when not to use' or comparison to siblings is provided.

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