Skip to main content
Glama
KazKozDev
by KazKozDev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

NameDescription
search_toolsC

Scalability feature: find the right tool for your complex task among all available tools.

get_document_structureA

Parses the Markdown file and returns a tree of headings and elements. Use this first to navigate.

search_textB

Performs a semantic search for text strings and returns their structural paths.

get_contextB

Returns the target element along with its immediate neighbors (before and after).

read_elementC

Fetches the full content of a specific block by its path.

replace_contentB

Overwrites the content of a specific block. Maintains document structure.

insert_elementB

Inserts a new block (heading, paragraph, etc.) relative to an existing one.

move_elementB

Moves an element (and its children) to a new location in the document.

delete_elementC

Removes a block from the document.

update_metadataB

Modifies the document's Frontmatter.

undoB

Reverts the last N operations on the document.

list_directoryB

Lists files and folders in the workspace.

create_fileD
create_directoryD
delete_itemD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.6/5.0

Scored across 15 tools

Disambiguation3/5

Most tools have distinct purposes, but there is notable overlap between delete_element and delete_item, which could cause confusion as their descriptions are unclear or missing. Additionally, search_tools is ambiguous and doesn't fit cleanly with the document editing focus, potentially leading to misselection.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., create_directory, insert_element, move_element) with only minor deviations like search_tools and undo, which are less structured but still readable. Overall, the conventions are predictable and aid in tool identification.

Tool Count5/5

With 15 tools, the count is well-scoped for a Markdown editor server, covering file management, document structure manipulation, content editing, and search functionalities. Each tool appears to serve a specific role without feeling excessive or insufficient for the domain.

Completeness4/5

The tool set provides comprehensive coverage for Markdown editing, including CRUD operations for files and elements, navigation, and undo functionality. A minor gap exists in lacking a dedicated tool for creating or modifying specific Markdown elements like lists or code blocks, but agents can work around this using insert_element and replace_content.