Skip to main content
Glama
dailydaniel

Logseq MCP Server

by dailydaniel
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

logseq_get_current_page

Retrieve the currently active page or block in your Logseq workspace using this tool, enabling streamlined interaction with your knowledge graph without requiring input parameters.

Instructions

Retrieves the currently active page or block in the user's workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/mcp_server_logseq/server.py:502-512 (handler)
    Main handler function in call_tool that executes the tool by calling Logseq API 'logseq.Editor.getCurrentPage' and formatting the result using format_no_arg_result.
    elif name == "logseq_get_current_page":
    args = GetCurrentPageParams(**arguments)
    result = make_request(
        "logseq.Editor.getCurrentPage",
        []
    )
    return [TextContent(
        type="text",
        text=format_no_arg_result(name, result)
    )]
  • src/mcp_server_logseq/server.py:94-96 (schema)
    Pydantic model defining the input schema for the tool (empty params).
    class GetCurrentPageParams(LogseqBaseModel):
    """Parameters for getting current page (no arguments needed)"""
  • src/mcp_server_logseq/server.py:238-242 (registration)
    Tool registration in the list_tools() function, defining name, description, and input schema.
    Tool(
    name="logseq_get_current_page",
    description="Retrieves the currently active page or block in the user's workspace",
    inputSchema=GetCurrentPageParams.model_json_schema(),
),
  • src/mcp_server_logseq/server.py:448-452 (helper)
    Helper lambda in format_no_arg_result that formats the output of logseq_get_current_page.
    'logseq_get_current_page': lambda r: (
    f"Current: {r.get('name', r.get('content', 'Untitled'))}\n"
    f"UUID: {r.get('uuid')}\n"
    f"Last updated: {r.get('updatedAt', 'N/A')}"
),

Tool Definition Quality

B3.2/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 of behavioral disclosure. It states the tool retrieves data, implying it's read-only, but doesn't clarify aspects like whether it requires user authentication, if it works offline, or what happens if no page is active. This leaves significant gaps for a tool that interacts with user workspace data.

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, clear sentence that directly states the tool's function without any fluff or redundancy. It's front-loaded and efficiently communicates the core purpose, 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 no parameters, no annotations, and no output schema, the description is minimally adequate but lacks completeness. It doesn't explain what 'currently active' means in context, what format the return value has, or how errors are handled, leaving the agent with unanswered questions about implementation details.

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 input schema has 0 parameters with 100% coverage, so the schema already fully documents that no arguments are needed. The description adds no parameter-specific information, but with zero parameters, the baseline is 4 as it doesn't need to compensate for any gaps.

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 tool's purpose with a specific verb ('Retrieves') and resource ('currently active page or block'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'logseq_get_page' or 'logseq_get_current_page_content', 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?

The description provides no guidance on when to use this tool versus alternatives like 'logseq_get_page' (which might retrieve a specific page) or 'logseq_get_current_page_content' (which might retrieve content instead of metadata). There's no mention of prerequisites, context, or exclusions.

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

Related 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/dailydaniel/logseq-mcp'

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