Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Upload temporary Tracker file

tracker_attachments_upload_temp

Upload a small base64-encoded temporary file to get a one-time attachment ID for adding it to a Yandex 360 Tracker issue or comment.

Instructions

Upload a small temporary file to attach when creating an issue or a comment.

The returned id goes into attachmentIds of the issue or comment body, and works once. The file travels as base64 in the request, so keep it small.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe file's bytes, base64-encoded.
filenameYesName of the file being uploaded.
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: -[
-  "file_name",
-  "data"
-]New value: +[
+  "filename",
+  "data"
+]
  2. First observedv0.67.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only give generic hints (readOnlyHint=false, openWorldHint=true, idempotentHint=false). The description adds non-obvious behavior: the returned id 'works once' (single-use token) and the payload travels as base64 so it must stay small. These are exactly the traits an agent needs and cannot infer from annotations or schema.

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 short sentences, front-loaded with the action and purpose, then the critical return-value usage and the size constraint. No filler; every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by explaining the returned id and its single-use nature, plus the base64 size constraint. For a 3-parameter upload tool, nothing an agent needs to call it correctly appears to be missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains where the returned id is consumed (attachmentIds of the issue/comment body) and the practical size constraint on the base64 data parameter.

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?

States a specific verb and resource (upload a temporary file) with the scope that distinguishes it from siblings: it is 'temporary', small, and intended for issue/comment attachment. An agent can separate it from tracker_attachments_upload and tracker_attachments_import based on the description alone.

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?

The description clearly frames the when: 'attach when creating an issue or a comment', and the returned id feeds 'attachmentIds' of that body. It does not explicitly contrast with tracker_attachments_upload or import, so it stops short of naming alternatives, but the intended workflow is unambiguous.

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