Skip to main content
Glama
Mad-Man-Dan

Karbon MCP Server

by Mad-Man-Dan

Upload a file

upload_file

Upload a file to Karbon and attach it to a work item, contact, organization, or client group. Requires at least one key; prefer file path to avoid base64 size limits.

Instructions

Upload a file to Karbon and attach it to a work item, contact, organization, or client group (at least one key is required). SIZE LIMITS: keep uploads small — Karbon rejects oversized uploads, and this server reads the whole file into memory. Prefer filePath (a path on the machine running this MCP server) whenever possible; only use contentBase64 for small files (roughly under 1 MB), because base64 inflates data ~33% and large payloads can exceed the AI client's message limits or be truncated mid-transfer. If a file seems large (tens of MB or more), tell the user to upload it through Karbon's own UI instead. SECURITY: only upload files the user explicitly pointed you to. Never upload configuration files, credential stores, environment files, keys, or anything the user has not named — uploading puts the file's contents in the Karbon tenant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNameNoFile name including extension. Required with contentBase64; defaults to the filePath basename otherwise.
filePathNoAbsolute path of the file on the machine running this MCP server (preferred)
contactKeyNo
workItemKeyNo
contentBase64NoBase64-encoded file content — small files only; requires fileName
clientGroupKeyNo
organizationKeyNo
Behavior5/5

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

No annotations provided, but description fully covers behavioral traits: size limits, memory usage, base64 inflation, truncation risks, and security restrictions. It warns against uploading sensitive files and describes server behavior.

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?

The description is somewhat verbose but well-structured: purpose, then size limits, preferences, caveats, and security. Each sentence adds value, though could be slightly more concise. Front-loaded with key information.

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?

Given 7 parameters, no annotations, and no output schema, the description covers purpose, attachment entities, size constraints, security, and fallback instructions. Minor gap: no mention of return value or success indicator, but overall comprehensive.

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

Parameters4/5

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

Schema coverage is 43%, but description adds meaning beyond schema: clarifies fileName requirement, labels attachment keys as required (at least one), explains when to use filePath vs contentBase64, and provides size guidelines. It 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?

Description clearly states the tool uploads a file to Karbon and attaches it to work items, contacts, organizations, or client groups. It distinguishes from siblings like download_file and other CRUD tools, providing specific verb+resource+attachment context.

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

Usage Guidelines5/5

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

Explicitly tells when to use (uploading to Karbon), when not to (for large files, direct user to Karbon UI), and provides size limits, preferred method (filePath), and base64 caveats. Offers alternatives and constraints.

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/Mad-Man-Dan/karbon-mcp-server'

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