Skip to main content
Glama
secemp9
by secemp9

kitty_create_marker

Create markers to highlight text patterns in a kitty window using literal strings, regular expressions, or custom Python functions.

Instructions

Create a marker that highlights text matching a pattern in a kitty window. Marker types: "text"/"itext" for literal matches, "regex"/"iregex" for regex matches, "function" for custom Python functions. Color groups 1-3 use different highlight colors as configured in kitty.conf.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selfNoTarget the window this command runs in.
matchNoWindow match expression.
marker_specYesMarker specification: first element is the type (text, itext, regex, iregex, function), followed by pairs of <color_group> <pattern>. Example: ["text", "1", "ERROR", "2", "WARNING"] or ["regex", "1", "\\bERROR\\b"]. Required.
Behavior3/5

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

No annotations provided, so description carries full burden. Explains that marker highlights text using types and colors, but does not disclose side effects, persistence, or whether markers replace existing ones. Adequate but not thorough.

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?

Two sentences: first states purpose, second lists types and color groups. No wasted words, front-loaded with key information.

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 no output schema and 3 parameters, description covers main purpose and marker types. Could mention marker lifetime or that they can be removed with kitty_remove_marker, but still reasonably complete.

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 coverage is 100% with detailed descriptions for all parameters, including marker_spec structure. Tool description adds minimal extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it creates a marker to highlight text matching a pattern. Mentions marker types and color groups. Does not explicitly differentiate from sibling kitty_remove_marker, but purpose is clear.

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

Usage Guidelines3/5

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

Implies usage for highlighting patterns, but no explicit guidance on when to use vs other tools like kitty_send_text or kitty_run. No exclusions or alternatives mentioned.

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/secemp9/kitty-mcp-server'

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