Skip to main content
Glama

nexus_list_keystones

Retrieve available NEXUS Keystone backups from WorkFlowy to restore or manage hierarchical data structures.

Instructions

List all available NEXUS Keystone backups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration for 'nexus_list_keystones' which delegates to the client implementation.
    @mcp.tool(
        name="nexus_list_keystones",
        description="List all available NEXUS Keystone backups."
    )
    def nexus_list_keystones() -> dict:
        """List all available NEXUS Keystone backups."""
        client = get_client()
        return client.nexus_list_keystones()
  • Core handler implementation: scans hardcoded backup directory for .json files, parses filename format into structured keystone metadata, returns sorted list.
    def nexus_list_keystones(self) -> dict[str, Any]:
        """List NEXUS Keystone backups."""
        backup_dir = r"E:\__daniel347x\__Obsidian\__Inking into Mind\--TypingMind\Projects - All\Projects - Individual\TODO\temp\nexus_backups"
        if not os.path.exists(backup_dir):
            return {"success": True, "keystones": [], "message": "No backup dir"}
        
        keystones = []
        for filename in os.listdir(backup_dir):
            if filename.endswith(".json"):
                parts = filename.replace('.json', '').split('-')
                if len(parts) >= 3:
                    keystones.append({
                        "keystone_id": parts[-1],
                        "timestamp": parts[0],
                        "node_name": "-".join(parts[1:-1]),
                        "filename": filename
                    })
        
        return {
            "success": True,
            "keystones": sorted(keystones, key=lambda k: k['timestamp'], reverse=True)
        }
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 of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't mention any constraints like pagination, sorting, filtering, or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool has 0 parameters and an output schema exists, the description covers the basic purpose adequately. However, without annotations and with sibling tools that suggest complex operations (e.g., 'nexus_purge_keystones'), more context on behavioral traits or usage scenarios would be beneficial for completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here, but doesn't explicitly state 'no parameters needed' to earn a perfect score.

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 clearly states the action ('List') and resource ('NEXUS Keystone backups') with the scope 'all available', making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'nexus_purge_keystones' or 'nexus_restore_keystone', which prevents a perfect score.

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 is provided on when to use this tool versus alternatives. While the name suggests it's for listing backups, there's no mention of prerequisites, timing considerations, or how it relates to other keystone-related tools like 'nexus_purge_keystones' or 'nexus_restore_keystone'.

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/daniel347x/workflowy-mcp-fixed'

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