Skip to main content
Glama

Set DAT content (whole)

set_dat_content
Destructive

Replace the entire contents of a Text or Table DAT with new text. Prevents empty or whitespace-only writes unless explicitly confirmed, avoiding accidental data loss.

Instructions

Overwrite a Text or Table DAT's entire .text with new content. Unlike edit_dat_content (which makes a surgical find-and-replace), this replaces everything in one shot — use it to deploy a full script or template. Refuses to write empty/whitespace-only text unless confirm_wipe:true is passed, preventing silent data loss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe full new contents of the DAT. Every existing character will be discarded; this string becomes the entire `.text` value.
dat_pathYesAbsolute path to the Text or Table DAT whose content will be fully replaced (e.g. '/project1/mytext1').
confirm_wipeNoSet true to allow writing empty or whitespace-only text, which clears the DAT. When false (default), the tool refuses to write blank content to prevent silent data loss.
Behavior5/5

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

Beyond the annotations (destructiveHint, readOnlyHint), the description discloses a safety guard: it refuses empty/whitespace-only text unless `confirm_wipe:true` is passed, and explains the rationale ('preventing silent data loss'). This adds meaningful behavioral context not present in the annotations.

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?

Three concise sentences, each adding essential information: purpose, differentiation/usage, and safety behavior. No 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?

For a destructive write operation with no output schema, the description fully covers the tool's function, appropriate use cases, and safety constraints, making it self-sufficient for an agent to decide when and how to invoke it.

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%, with each parameter already well-documented. The description reiterates the `confirm_wipe` role but introduces no new parameter semantics beyond the schema.

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 uses a specific verb ('Overwrite') and resource ('Text or Table DAT's entire .text'), and explicitly contrasts with `edit_dat_content` for surgical edits, clearly distinguishing its scope.

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 explicitly names the alternative sibling tool `edit_dat_content` and states when this tool is preferred ('use it to deploy a full script or template'), plus explains the `confirm_wipe` condition for blank content.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server