Skip to main content
Glama
Sign In
RunComfy MCP

RunComfy MCP

Official
by runcomfy-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

upload_dataset_text_file

Destructive

Add a caption text file to a dataset directly from inline text, avoiding the need to host files. Provide dataset ID, a filename matching the media, and the caption body.

Instructions

Add a text file — normally a caption — to a dataset.

Backs ``POST /prod/v1/trainers/datasets/{dataset_id}/upload`` with
inline text, so captions can be written without hosting a file.

Args:
    dataset_id: Target dataset.
    filename: Must share the base name of the media it captions:
        ``img_0001.jpg`` → ``img_0001.txt``.
    text: Caption body.

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": {
      "dataset_id": "<dataset_id>",
      "filename": "<filename>",
      "text": "<text>"
    },
    "name": "upload_dataset_text_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
filenameYes
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior2/5

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

Annotations include destructiveHint=true, but the description only says 'Add' and does not clarify whether uploading a filename that already exists overwrites, errors, or creates a duplicate. No side effects, overwrite behavior, or mutation details are disclosed, leaving an important behavioral gap for a tool marked as destructive.

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 compact and front-loaded with the purpose, then gives endpoint context and a tight parameter list. Every sentence earns its place, and the filename example replaces longer prose.

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 simple three-string-parameter upload, the description covers what, how, and the filename convention, and the annotations cover safety. The main missing piece is behavior when an existing caption file shares the same filename, especially given destructiveHint=true.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and succeeds. It documents all three parameters, including the critical filename constraint with a concrete example (img_0001.jpg → img_0001.txt), which is essential for correct usage.

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 clearly states the action and resource: 'Add a text file — normally a caption — to a dataset.' It also distinguishes itself by emphasizing inline text uploads 'without hosting a file,' which separates it from the sibling upload_dataset_file_from_url. This is specific, unambiguous, and differentiable.

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 gives a clear use context: write captions inline rather than hosting files. It implies the alternative (hosting a file) without explicitly naming upload_dataset_file_from_url or stating a when-not rule. The guidance is useful but not fully explicit about alternatives.

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