Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Attach file to Tracker issue

tracker_attachments_upload

Upload a small file to a Tracker issue by sending base64 data, and get the created attachment back. Use for quick issue attachments; for large files, run the CLI upload command.

Instructions

Attach a small file to a Tracker issue; returns the created attachment.

The file travels as base64 in the request, so keep it small; for a large file run ycli tracker attachments upload instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe file's bytes, base64-encoded.
filenameYesName of the file being uploaded.
issue_keyYesIssue key or id, e.g. ``JUNE-2``.
rename_toNoStore the file under this name instead of ``filename``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • removedInput schema / properties / file_name
      Removed value: -{
-  "description": "Name of the file being uploaded.",
-  "type": "string"
-}
    • addedInput schema / properties / filename
      Added value: +{
+  "description": "Name of the file being uploaded.",
+  "type": "string"
+}
    • changedInput schema / properties / rename_to / description
      Previous value: -"Store the file under this name instead of ``file_name``."New value: +"Store the file under this name instead of ``filename``."
    • changedInput schema / required
      Previous value: -[
-  "issue_key",
-  "file_name",
-  "data"
-]New value: +[
+  "issue_key",
+  "filename",
+  "data"
+]
  2. First observedv0.67.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true). The description adds useful context beyond that: the payload travels base64 and must be small, and the call returns the created attachment. It omits permissions/rate-limit details but the annotation bar is already met.

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?

Two tight sentences: purpose front-loaded, then the size constraint and fallback. Every sentence earns its place with no redundancy.

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-param mutation tool with no output schema, the description covers the essential constraint (base64/small payload) and even states the return value. Auth/permission expectations are not covered, but it's complete enough to call correctly.

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 schema already documents data, filename, issue_key, and rename_to. The description's mention of base64 adds nothing beyond the data param's format=base64 in the schema. Baseline 3 is appropriate when the schema carries parameter semantics.

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?

States a specific verb and resource ('Attach a small file to a Tracker issue') and even notes the return ('returns the created attachment'). It does not explicitly differentiate from close siblings like tracker_attachments_upload_temp or tracker_attachments_import, though the 'small file' framing hints at the distinction.

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?

Gives a concrete usage condition ('keep it small') and names an alternative path ('for a large file run ycli tracker attachments upload'). It stops short of routing the agent among the MCP siblings (upload_temp, import), so it's clear context rather than full when/when-not coverage.

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