Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Add attachment to TP card

add_attachment

Attach a file to a Targetprocess card by ID using a server-side file path or base64 content and filename for chat-uploaded images.

Instructions

Upload a file (e.g. a screenshot or mockup) as an attachment on a Targetprocess card (bug, user story, feature, etc.) by its ID. filePath is read from THIS MCP SERVER'S OWN filesystem, not the calling assistant's — it only works for a file already on this machine. For an image attached/pasted/uploaded directly in the chat, read its bytes yourself and pass fileContent (base64) + fileName instead; passing that attachment's sandboxed path as filePath will fail with "file not found".

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": {
      "cardId": "<cardId>"
    },
    "name": "add_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesTP card ID to attach the file to, e.g. 145789
fileNameNoFile name to use when uploading via fileContent, e.g. screenshot.png
filePathNoAbsolute path to a file on this MCP server's own filesystem. Do not use this for a file that only exists in the calling assistant's sandbox (e.g. a chat-attached image) — use fileContent instead.
fileContentNoBase64-encoded file content; use together with fileName. This is the reliable option for an image that came from a chat attachment/upload rather than a path already on this machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it discloses that filePath resolves against the MCP server's own filesystem rather than the caller's sandbox, and it names the concrete failure mode ('file not found') from the wrong usage. It omits other traits such as size limits, permission requirements, whether an attachment replaces or coexists with existing ones, and what the call returns.

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?

Three tight sentences, front-loaded with what the tool does before the filePath caveat and the fileContent alternative. Every sentence carries operational information; nothing is redundant boilerplate.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers the main failure mode and both input modes, which is the critical knowledge. It falls short of full completeness by not indicating the result of a successful upload or any constraints such as file size or supported types.

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 description coverage is 100% and the schema already explains filePath vs fileContent vs fileName in nearly the same terms. The description reinforces the pairing of fileContent with fileName and adds the rationale, but adds little semantic detail beyond the structured fields, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Upload a file ... as an attachment on a Targetprocess card') and names the card types it applies to (bug, user story, feature). It is unmistakably distinct from sibling write tools like add_comment or create_card_relation.

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?

It gives explicit routing conditions between the two input modes: filePath for files already on the server, fileContent + fileName for chat-attached images whose bytes the caller must read. It also warns that passing a sandboxed path as filePath will fail. It does not, however, frame when to prefer this tool over other card-modification siblings, though no obvious competing attachment tool exists.

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

Deploy Server

Other Tools