HAOps MCP Server

haops_upload_help_image

Upload base64-encoded images to help articles for embedding in content. Returns attachment URL.

Instructions

Upload an image to a help article. Accepts base64-encoded image data. Admin-only. Returns the attachment record with a URL for embedding in content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "articleSlug": "<articleSlug>",
      "imageBase64": "<imageBase64>",
      "filename": "<filename>",
      "mimeType": "<mimeType>"
    },
    "name": "haops_upload_help_image"
  }
}

Input Schema

Name	Required	Description
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`filename`	Yes	Filename with extension (e.g. screenshot.png)
`mimeType`	Yes	Image MIME type
`articleSlug`	Yes	The help article slug
`imageBase64`	Yes	Base64-encoded image data

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Without annotations, the description carries the burden of behavioral disclosure. It states it uploads (mutation), requires admin privileges, accepts base64 data, and returns an attachment record with a URL. This is clear and adequate, though it does not mention potential side effects or limits.

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?

The description is only three sentences, no redundant words, and front-loads the main purpose. Every sentence adds value without being 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?

The description covers the action, input format, access restriction, and return value. Without an output schema, it provides enough context for a simple upload tool. However, it does not differentiate from similar sibling tools or mention any limitations (e.g., file size), leaving some uncertainty.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond what the schema already provides for each parameter. The mention of 'base64-encoded image data' and 'Admin-only' provides context but not parameter-specific details beyond the schema.

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

Purpose4/5

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

The description clearly states the action and resource ('Upload an image to a help article'), but does not differentiate from the sibling tool 'haops_upload_doc_image', which could cause confusion for an AI agent selecting between them.

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?

The description mentions 'Admin-only' as a prerequisite and specifies that it accepts base64 data, but does not provide guidance on when to use this tool versus alternatives like 'haops_upload_doc_image' or when not to use it.

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

Deploy Server