Skip to main content
Glama

Bu dosyanın ad eşleşmelerini kalıcı sil

forget_matter
DestructiveIdempotent

Permanently deletes a matter file’s local placeholder mappings, making the removed placeholders unrecoverable; use it to clean up case data after finalizing documents.

Instructions

Bir dosyanın (matter) yerel yer tutucu eşleşmelerini kalıcı olarak siler. Sonrasında bu yer tutucular geri konamaz.

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": {
      "matter": "<matter>"
    },
    "name": "forget_matter"
  }
}

Input Schema

NameRequiredDescriptionDefault
matterYesMatter (dosya) label; files of the same case share placeholders. Use a neutral label such as a file number, not a client name.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already carry destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the risk profile is known. The description adds genuine value by making irreversibility explicit ('Sonrasında bu yer tutucular geri konamaz') and by scoping the effect to local placeholders only. However, it does not say whether the underlying file or other state is affected, nor what the caller receives back.

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?

Two short sentences, no filler: the action is front-loaded and the irreversibility warning follows immediately. Nothing in the text could be removed without losing 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 destructive, single-parameter tool with annotations covering destructive/idempotent semantics and full schema coverage, the definition supplies enough to call it safely. The gap is that the term 'yerel yer tutucu eşleşmeleri' remains jargon and no return value is described, though no output schema exists to cover that.

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% and the single 'matter' parameter is already documented in detail, including a warning to use a neutral label rather than a client name. The description adds only that matches are scoped per file ('bir dosyanın'), which does not go beyond the schema's own explanation of shared placeholders across a case.

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?

States a specific verb ('kalıcı olarak siler') and a specific resource ('yerel yer tutucu eşleşmeleri'), and the parenthetical '(matter)' ties it to the matter concept used by siblings like restore_to_file and mask_file. It stops short of explicitly contrasting itself with those siblings, but the destructive/permanent framing makes the operation distinguishable.

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

Usage Guidelines2/5

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

The description says what happens after the call ('geri konamaz') but never says when to choose this tool over alternatives such as restore_to_file or write_masked_copy, nor any precondition or confirmation requirement before a permanent deletion. The agent must infer the usage context from sibling names alone.

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