Skip to main content
Glama
Datris MCP Server

Datris MCP Server

suggest_field_protection

Suggests per-field protection methods (hmac, mask, redact, drop, none) with a one-line reason from field names and types only, so you can review and choose protections before creating a pipeline.

Instructions

Suggest per-field protection (hmac, mask with an optional preserve, redact, drop, or none, each with a one-line reason) for a pipeline's source fields, computed by the configured CodeGen model from field NAMES and TYPES ONLY: no row value is sent to the model. Stateless: nothing is saved or changed. Pass pipeline (an existing pipeline name; its stored source schema is used) or fields (an array of {name, type}, e.g. the schema you are about to create). A field that already carries protect shows it as current next to the suggestion. Show the suggestions to the user and ask which to accept before passing any of them as the protect map to create_pipeline; never apply them on your own. With preset (delimited sources only) the server's rule-based preset classifier is used instead of the model: each field gets an identifier class, a method and a reason, and the result lists the fields it did not recognise and review notes; show all of it, including the review notes, to the user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "suggest_field_protection"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoFields to classify (use this OR pipeline): [{"name": ..., "type": ...}]
presetNoOptional preset to classify against instead of the model (delimited/CSV sources only). The result can be enforced on create_pipeline with protect_preset.
pipelineNoExisting pipeline name (use this OR fields)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses the privacy boundary ('no row value is sent to the model'), the statelessness ('nothing is saved or changed'), the `current`-vs-suggestion comparison, and that the preset path is rule-based and returns unrecognised fields plus review notes. It stops short of stating auth requirements, rate limits, or failure modes, but the core behavioral contract a caller needs is present.

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 key facts — what it does, the privacy guarantee, the statelessness, and the pairing of `pipeline` vs `fields` — are front-loaded. It runs long as a single dense paragraph with a semi-colon-chained caveat about user approval, which is all load-bearing but could be split for scanability.

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, and the description compensates by describing the return shape in both modes: per-field method with a one-line reason and an optional `current` value, or for presets an identifier class, method, reason, unrecognised fields, and review notes. For a read-only stateless suggestion tool, nothing an agent needs in order to call it correctly is 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 coverage is already 100%, so the baseline would be 3, but the description adds meaning the schema does not: `pipeline` resolves an existing pipeline's stored source schema, `fields` is framed as 'the schema you are about to create', and `preset` is limited to delimited/CSV sources with results enforceable via protect_preset. That materially clarifies each parameter's role beyond its one-line schema text.

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 opens with a specific verb+resource: 'Suggest per-field protection ... for a pipeline's source fields', and enumerates the possible outcomes (hmac, mask with optional preserve, redact, drop, none) plus the basis of computation (field names and types only). It is unmistakable what this tool produces and how it differs from a mutation like create_pipeline.

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?

It states the two mutually exclusive input modes ('Pass `pipeline` ... or `fields`'), the condition that selects the preset path ('delimited sources only'), and an explicit workflow constraint: show suggestions to the user, ask which to accept, then pass them to create_pipeline, 'never apply them on your own'. That is when-to-use, when-not, and the downstream handoff all in one.

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