Skip to main content
Glama
JeanFrancoisGagne

crapkit

by JeanFrancoisGagne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Near-duplicate function pairs

list_duplicate_functions
Read-onlyIdempotent

Find near-duplicate function pairs in the newest run (up to 50) before refactoring so duplicate code can be merged.

Instructions

Lists near-duplicate function pairs in the newest run, at most 50. Use it before a refactor so twins are folded together, and get_function_brief for one function's twins. It reads the run's stored index, whose first build takes seconds on a large repo, skips functions with under 8 lines of their own and nested pairs, and an empty list means no pair reached similarity. similarity is shared shingles over the smaller function: 1.0 admits only a function found whole inside another, 0.8 four lines in five, and repo may be any directory under the checkout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNopath to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory
similarityNocontainment threshold, shared over smaller, 0 to 1 (default 0.8)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairsNopairs at or above similarity, best containment first, at most 50
run_idNothe newest run whose rows were compared
schemaNopayload schema version, 1
truncatedNopresent only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI command that prints the whole answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.1
    • changedInput schema / properties / repo / description
      Previous value: -"path to the scored repo's root (default: the repo the server was started in)"New value: +"path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory"
    • addedOutput schema / properties / truncated
      Added value: +{
+  "description": "present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI command that prints the whole answer",
+  "properties": {
+    "fields": {
+      "additionalProperties": {
+        "properties": {
+          "kept": {
+            "description": "how many the answer keeps",
+            "type": "integer"
+          },
+          "of": {
+            "description": "how many the whole answer has",
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "description": "each cut field, named by its keys joined with dots (gate.breaches) -> kept and of: elements for a list, entries for an object, characters for a string",
+      "type": "object"
+    },
+    "full": {
+      "description": "the crapkit command that prints the whole answer, spelled for the server's shell",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Addedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, but the description adds behavior they cannot: it reads a stored run index whose first build takes seconds on a large repo, skips functions under 8 lines and nested pairs, and defines what an empty result means. This is substantial operational context beyond the annotation set.

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?

Front-loaded with purpose and cap, then usage, then behavior and the threshold semantics. It is a dense multi-clause run-on, but nearly every clause carries information an agent needs; no filler sentences.

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?

An output schema exists, so return format need not be described, and the description still covers the count cap, the empty-list case, threshold semantics, index-build latency, and excluded items. Nothing an agent needs to call and interpret this 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 description coverage is 100%, so the baseline is 3, but the description genuinely extends meaning: it concretizes the similarity scale ('1.0 admits only a function found whole inside another, 0.8 four lines in five') and clarifies that repo may be any directory under the checkout. It stops short of restating the default or the ~ expansion, which live in 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?

States a specific verb and resource ('Lists near-duplicate function pairs in the newest run, at most 50') and immediately distinguishes itself from get_function_brief, which handles a single function's twins. An agent can tell what it returns and how it differs from its sibling without opening either schema.

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

Usage Guidelines4/5

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

Gives a clear triggering context ('Use it before a refactor so twins are folded together') and routes to the per-function alternative (get_function_brief). It does not state any when-not condition or prerequisite beyond that, so it falls just short of the full when/when-not/alternatives bar.

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