Markdown-To-Notion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| markdown-to-notionC | Convert markdown content to notion json page content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is singular and clearly defined, eliminating any ambiguity in tool selection.
Since there is only one tool, it inherently maintains perfect consistency with itself. The tool name follows a clear verb-object pattern (markdown-to-notion), which is straightforward and descriptive for its function.
A single tool is generally too few for a server's scope, as it limits functionality and suggests an incomplete or overly narrow implementation. While the tool's purpose is clear, one tool often indicates a minimal surface that may not cover related operations or workflows effectively.
The server's domain appears to involve converting markdown to Notion content, but with only a conversion tool, there are significant gaps. Missing operations might include retrieving markdown, updating Notion pages, handling errors, or managing conversions in bulk, which could lead to agent failures in broader tasks.