Skip to main content
Glama

cluster_rebind

Propose, apply, list orphan papers, or check rebind status for paper-to-cluster moves in one action-based workflow.

Instructions

Run the cluster-rebind workflow specified by action.

Single entrypoint that consolidates four legacy rebind operations (propose / apply / list_orphans / status) into one tool with an action discriminator. Replaces the deprecated aliases propose_cluster_rebind / apply_cluster_rebind / list_orphan_papers / summarize_rebind_status, which are gated behind RESEARCH_HUB_MCP_INCLUDE_DEPRECATED=1 and slated for removal in v2.0.0.

When to use:

  • After ingest leaves orphan paper notes that don't match any active cluster, and you want to plan moves before touching files.

  • After a manual cluster rename, when existing paper notes still reference the old slug.

  • Periodic vault hygiene: surface stuck or low-confidence orphans via action='status'.

When NOT to use:

  • You want to delete clusters wholesale, not rebind their papers; use research-hub clusters delete (CLI) instead.

  • You want to archive papers carrying a label; use prune_cluster instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoWhich rebind sub-step to run. One of: ``'propose'`` (write a draft rebind report to disk), ``'apply'`` (execute moves from a report — requires ``report_path``), ``'list_orphans'`` (return orphan paper paths, optionally filtered by ``folder``), or ``'status'`` (one-shot summary of orphans + open proposals). Defaults to ``'propose'``.propose
cluster_slugNoLimit ``propose`` / ``status`` to one cluster's papers. Empty string (default) means all clusters.
report_pathNoPath to a rebind report emitted by a prior ``action='propose'``. Required for ``action='apply'``; ignored otherwise.
dry_runNoWhen ``action='apply'``, report the moves without touching the filesystem. Defaults to ``True`` — pass ``False`` to actually move files.
auto_create_newNoWhen ``action='apply'``, allow the apply step to create previously-unknown cluster folders for high-confidence new-cluster proposals. Defaults to ``False``.
folderNoWhen ``action='list_orphans'``, restrict the result to papers under this ``raw/`` subdirectory. Empty string (default) returns all orphans.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the tool as a single entrypoint and mentions the deprecated aliases, but does not explicitly state the potential destructive nature of the 'apply' action when 'dry_run' is false. More explicit warnings about side effects would improve transparency.

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?

The description is well-structured with sections, front-loading the core purpose. While it is moderately lengthy, each sentence adds value by explaining actions, usage guidance, and deprecation details. It is concise relative to the tool's complexity.

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?

Given the tool's complexity (6 parameters, 0 required, 100% schema coverage, and an output schema), the description covers workflow, usage guidance, parameter context, and deprecation details. It is complete enough for effective tool selection and invocation.

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%, so the schema already documents each parameter thoroughly. The description adds context about the overall workflow and action selection, but does not significantly enhance understanding of individual parameter meanings beyond 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?

The description clearly states that the tool runs the cluster-rebind workflow specified by an action, consolidating four legacy operations. It lists specific use cases and distinguishes from siblings like 'prune_cluster' and CLI delete.

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

Usage Guidelines5/5

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

The description includes explicit 'When to use' and 'When NOT to use' sections, providing concrete scenarios and naming alternative tools (e.g., 'research-hub clusters delete', 'prune_cluster'). This provides clear guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WenyuChiou/research-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server