Skip to main content
Glama

Keep one copy of a duplicate

keep_one_of_family
Destructive

Keep one copy of a duplicate family, remove extras. confirm=true required.

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": {
      "copyId": "<copyId>",
      "confirm": "<confirm>"
    },
    "name": "keep_one_of_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
copyIdYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds that extras are removed and that confirmation is mandatory. It still leaves the crucial behavior unspecified: which copy survives, whether copyId identifies the survivor or the family, and whether removal is permanent.

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?

Two short sentences, effect first and precondition second, with no filler. Its brevity borders on under-specification, but nothing written is wasted.

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

Completeness2/5

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

For a destructive mutation with zero schema description coverage and no output schema, the description is too thin. It omits survivor-selection semantics, permanence of the removal, and any indication of what the call returns, all of which an agent needs before invoking an irreversible tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the whole burden and it only partly does: 'confirm=true required' clarifies confirm, but copyId is never explained. An agent cannot tell from the text whether copyId is the copy to keep or a family/group identifier.

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 gives a specific verb and resource ('keep one copy of a duplicate family') plus the net effect ('remove extras'), so the de-duplication purpose is unmistakable. It does not name or distinguish itself from nearby siblings such as remove_copy or list_doubles, which keeps it just short of a 5.

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?

There is no guidance on when to choose this over remove_copy, or on the typical workflow of listing doubles first. The only guidance is a hard precondition ('confirm=true required'), which is a prerequisite rather than a when-to-use signal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.