Skip to main content
Glama
Datris MCP Server

Datris MCP Server

upload_config

Upload base64-encoded configuration files to Datris, including JSON Schema validation schemas for pipeline data quality checks.

Instructions

Upload a configuration file to the Datris platform. Supports 'validation-schema' (JSON Schema files used in pipeline dataQuality schema validation). Send the file content as base64. 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>",
      "type": "<type>"
    },
    "name": "upload_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesConfig file type: 'validation-schema' for JSON Schema
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., schema.json, transform.js)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a strong job on the non-obvious approval branch: it explains that the call may return 'pending_approval' with an 'approvalId', instructs the agent to tell the user, poll get_approval with wait_seconds, and not re-issue the action. It omits normal success behavior, overwrite semantics, and validation-failure behavior.

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 description is front-loaded with purpose and supported type, then covers the important approval workflow. It is dense but largely free of filler; the approval instructions are necessary, though a single paragraph makes it slightly harder to scan.

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 tool with no annotations and no output schema, the description covers the critical conditional approval flow and the required base64 content format. It still leaves the normal success response and overwrite/validation-failure behavior unspecified, which is a meaningful gap but not enough to make the definition inadequate.

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%, so all four parameters are already documented, including the enum for 'type' and the audit-log purpose of 'reason'. The description only repeats that content is base64 and that 'validation-schema' is supported, adding little meaning beyond the schema.

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?

The description states a specific verb and resource: upload a configuration file to the Datris platform. It also scopes the supported file type to 'validation-schema' and explains its use in pipeline dataQuality schema validation, which distinguishes it conceptually from upload_data, though no sibling is named explicitly.

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 clear context for when to use the tool: uploading JSON Schema validation-schema files for pipeline dataQuality validation. It does not explicitly say when not to use it or name an alternative for other file types, so it falls short of full when/when-not guidance.

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