Skip to main content
Glama
Datris MCP Server

Datris MCP Server

upload_data

Send a whole base64-encoded file to a registered pipeline in one call for schema validation, transformation, vector chunking, and routing; returns a token to track job status.

Instructions

Upload data to a registered pipeline for processing. Send the ENTIRE file content as a single base64-encoded string in ONE call — do not pre-split or chunk the content client-side. Vector destinations (pgvector, qdrant, weaviate, milvus, chroma) apply recursive chunking server-side using the pipeline's configured chunkSize/chunkOverlap; for those, one upload_data call yields many embedded chunks automatically. The pipeline's rules are applied: schema validation, data quality checks, transformations, then routing to the configured destination. A Live Read (scratch) pipeline validates or transforms the file and hands the rows back (status rollup resultPreview, then get_pipeline_result) instead of landing them. Returns a pipelineToken for tracking job status via get_job_status. If this Datris instance's agent policy requires a person to approve this action, the call does NOT perform it: it returns status pending_approval with an approvalId. Tell the user it is waiting for approval in Datris, then poll get_approval with that id (pause with wait_seconds between polls) — do not re-issue the action.

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": {
      "content": "<content>",
      "filename": "<filename>",
      "pipeline": "<pipeline>"
    },
    "name": "upload_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.
contentYesBase64-encoded file content
filenameYesFilename (e.g., data.csv, report.json, orders.xml)
pipelineYesPipeline name to process the data with

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so thoroughly: it discloses server-side recursive chunking, the ordered rule sequence (schema validation, quality checks, transformations, routing), the divergent behavior of `scratch` pipelines, and the approval-gated path that returns `pending_approval` without performing the action. It even instructs not to re-issue the action, which is exactly the failure mode an agent would otherwise hit.

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 definition is dense but front-loaded: the upload instruction and the anti-chunking rule come first, followed by downstream processing behavior and then the approval escape hatch. Some sentences are long and could be split, but no sentence is filler.

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?

There is no output schema, so the description must cover return values and it does: `pipelineToken` for job tracking, `resultPreview` for Live Read pipelines, and `pending_approval` with `approvalId`. Combined with the processing pipeline and approval-flow detail, an agent has everything needed to call this correctly and handle both terminal paths.

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 100%, so the baseline is 3, but the description adds real meaning for `content`: it must be the entire file, base64-encoded, in a single call, and must not be chunked. That constraint is not derivable from the schema's terse 'Base64-encoded file content'. It does not elaborate on `filename` or `pipeline` beyond the schema, so it is not a 5.

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: 'Upload data to a registered pipeline for processing.' An agent immediately knows this ingests file content into a pipeline, which separates it from configuration-oriented siblings like upload_config. It stops short of explicitly naming the sibling it is not, so it lands just below the top mark.

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?

Gives explicit operational guidance: send the ENTIRE file in one base64 string, do not pre-split or chunk client-side, and explains that vector destinations handle chunking server-side. It also routes the agent to get_pipeline_result for Live Read pipelines, to get_job_status via the pipelineToken, and to get_approval when the action is held for approval.

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