Skip to main content
Glama
Sign In
kodza

kodza

by kodza-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Search Kodza components

search_components
Read-only

Find Kodza UI components by describing what they do or look like; get slugs to fetch exact HTML, CSS, and JavaScript files.

Instructions

Find Kodza UI components (plain HTML/CSS/vanilla JS) by what they do or look like, e.g. "button fill hover", "image slider", "sticky header", "date picker". An empty query lists a whole category. Returns the slugs get_component takes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results, 12 by default
queryNoWords describing the component or effect, in English
categoryNobuttons, links, text, images, cards, navigation, scroll, transitions, forms, overlays, feedback or data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, openWorldHint=false), so the lower bar applies. The description still adds useful behavior: the component technology, the empty-query semantics, and the shape of the return value (slugs), which the agent needs to chain into get_component. It says nothing about ranking, matching strategy, or truncation beyond the limit default.

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?

Three short sentences, front-loaded with purpose, then examples, then the empty-query rule and the return contract. Every sentence carries information the agent needs; nothing is redundant with the title.

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?

For a zero-required-param search tool with no output schema, the description adequately covers purpose, query syntax, category fallback, and return type. Only minor gaps remain: no note on result ordering or what happens when limit exceeds available matches.

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?

Schema description coverage is 100%, so baseline is 3; the description earns extra by showing what a query string looks like ('button fill hover', 'sticky header') and by explaining the no-query case against the category parameter, which the schema does not spell out.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (find Kodza UI components) and pins the domain with '(plain HTML/CSS/vanilla JS)' plus four concrete query examples, so the agent knows exactly what it searches over. It also explicitly distinguishes itself from the sibling by noting it returns the slugs that get_component consumes.

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

Usage Guidelines4/5

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

Gives clear when-to-use context ('by what they do or look like') and the edge-case rule 'An empty query lists a whole category', which selects behavior the agent would otherwise have to guess. It does not explicitly say when NOT to use it, though the mention of get_component implicitly frames the browse-then-fetch workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools