Skip to main content
Glama

Maskeli kopyasını kaydet

write_masked_copy

Creates a locally masked .docx, .udf, or .txt copy of a legal document, replacing personal data with placeholders so AI tools can review it without seeing original values.

Instructions

Katip KVKK kapsamındaki kişisel verileri bu bilgisayarda çıkarır; Claude, Katip'in bulduğu değerlerin yerine yer tutucuları görür. .docx, .udf ya da .txt dosyasının maskeli kopyasını aynı biçimde aslının yanına kaydeder (ad.maskeli.uzantı). Hiçbir dosyanın üzerine yazmaz.

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": {
      "bilgi": "<bilgi>"
    },
    "name": "write_masked_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
belgeNolist_files'taki kısaltılmış ad (ör. "… - Vatandaşlık Dava Dilekçesi.udf"); onay kutusunda kullanıcıya gösterilir
bilgiYesAlways send exactly this text; it tells the user what Katip does.Belge bu bilgisayarda açılır ve maskelenir; Claude, Katip'in bulduğu kişisel verilerin yerine [AD SOYAD-1] gibi yer tutucuları görür. Katip bazı değerleri kaçırabilir.
matterNoMatter (dosya) label; files of the same case share placeholders. Use a neutral label such as a file number, not a client name.default
file_idNoId from list_files (preferred: keeps the file name private)
profileNoai = Yapay zekâ ile paylaşım (default: all personal data, the whole address, case and bar numbers); court = Mahkemeye sunum (parties' own addresses, UETS and bar numbers masked; the disputed property's address, case numbers and dates stay readable); anon = Tam anonim (also dates, provinces, courts, companies and institutions).ai
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's real contribution is the guarantee 'Hiçbir dosyanın üzerine yazmaz' (never overwrites) plus the exact output location and naming. It still leaves unclear what happens if a masked copy already exists (consistent with idempotentHint=false) and what the tool returns.

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?

Three tight sentences with no filler, and the no-overwrite guarantee is placed last as a closing safety note. The action verb arrives only in the second sentence because the privacy model is front-loaded, so it is slightly back-weighted rather than optimally front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter write tool with no output schema, the description covers where the file lands and that nothing is overwritten, which is the essential behavior. It omits what the call returns (e.g. the new file path) and any signal about masking profiles, leaving a moderate gap.

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 71%, with enum and default semantics already documented for profile, matter, belge and file_id inside the schema. The description adds only the output naming convention, which indirectly explains output_path; the undescribed path and output_path parameters gain no clarity from the text.

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 names a concrete action (saving a masked copy) and resource (a .docx/.udf/.txt file), and specifies the output naming pattern 'ad.maskeli.uzantı'. It does not differentiate this from the similarly named sibling mask_file, so an agent cannot tell from this text alone which of the two to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the reader can infer this is the tool to use when a masked duplicate must be persisted to disk next to the original. There is no explicit when-to-use, no when-not-to-use, and no reference to alternatives such as mask_file or restore_to_file.

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