Skip to main content
Glama
Datris MCP Server

Datris MCP Server

update_secret

Update AI provider secrets in Datris to configure API keys, endpoints, and models for AI profiling, schema generation, transformations, and RAG.

Instructions

Update an AI provider secret in the Datris platform. Use this to configure your AI API keys so Datris can use AI features (data profiling, schema generation, AI transformations, RAG). Only AI-related secrets can be updated: anthropic, openai, azure, grok, ollama, embedding. 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": {
      "name": "<name>",
      "fields": "<fields>"
    },
    "name": "update_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSecret name: anthropic, openai, azure, grok, ollama, or embedding
fieldsYesKey-value fields to set. Typical fields: endpoint (API URL), model (model name), apiKey (API key)
reasonNoOptional one-line reason for this change, recorded in the platform's audit log and shown to anyone asked to approve it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 burden and does well: it discloses the non-obvious agent-policy approval path, the exact return shape (`pending_approval` plus `approvalId`), and the required follow-up behavior. It stops short of stating whether `fields` merges with or replaces existing secret values, and says nothing about required permissions or whether the change is reversible.

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?

Front-loaded with purpose, then scope restriction, then the approval branch — a sensible order with no filler. The approval paragraph is long but each sentence (what is returned, what to tell the user, how to poll) carries distinct operational information.

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 mutation tool with no annotations and no output schema, the description covers the safety-critical behavior (approval gate, return status, polling loop) and the resource restriction. The remaining gap is write semantics — whether fields are additive or overwrite — which matters for an update operation but is a narrower omission than the ones it does address.

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% and the description adds essentially nothing beyond it — the enum list restates the `name` enum, and the typical field contents (endpoint, model, apiKey) are already documented in the schema. Baseline 3 applies since the schema does the heavy lifting, but no extra meaning (e.g. merge vs. replace semantics for `fields`) is contributed.

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 ("Update an AI provider secret in the Datris platform") and immediately scopes the resource to AI provider credentials with an explicit enumerated allow-list. This distinguishes it from the tap-secret siblings (create_tap_secret, delete_tap_secret, update_tap) without needing their schemas.

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 positive when-to-use guidance (configure AI API keys so Datris can use profiling, schema generation, transformations, RAG) and a hard exclusion (only the six listed AI secrets). It also gives explicit routing for the deferred case: do not re-issue, poll get_approval with wait_seconds — a named alternative with a named condition.

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