Skip to main content
Glama
Sign In
linklore

linklore

Official
by linklore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cleanup

Find duplicate lore or doc entries in AI-native memory by similarity threshold, helping you identify redundant items for cleanup.

Instructions

[read-only] cleanup(type='lore'|'doc') threshold(=0.85), status(=open), help - duplicate candidates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
helpNo
typeNolore
statusNoopen
thresholdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only declares '[read-only]' but does not disclose other behavioral traits such as required permissions, side effects, or what 'duplicate candidates' means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (one line) but at the cost of clarity. The notation is compact and front-loaded with '[read-only]', but key information is missing.

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?

Given 4 parameters and an output schema, the description is insufficient. It does not explain the purpose, return value, or how this tool fits among 23 siblings. Minimal context provided.

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 0%, so description must compensate. It lists defaults and hints at allowed values for 'type' (lore|doc), but does not explain the meaning of 'threshold', 'status', or 'help'. Some added value but incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description fails to specify a clear action verb. It states 'cleanup - duplicate candidates' but does not indicate whether the tool lists, identifies, or removes duplicates. The '[read-only]' prefix hints at no mutation, contradicting the typical meaning of 'cleanup.'

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?

No guidance on when to use this tool versus siblings like 'doctor', 'show', or 'status'. The description only lists parameter defaults without any contextual advice.

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