Skip to main content
Glama

Set up Klarhimmel UI in a project

setup
Read-only

Read-only and free. Returns the setup steps (the text of /setup.md) for adding Klarhimmel UI to a React project: Tailwind, alias, components.json, first block, tokens, design skill. Follow them once per project.

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": "setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with "Read-only and free," adding a cost dimension the annotations do not express. More importantly, with no output schema it discloses what is actually returned (the text of /setup.md) and what that text contains, which is exactly the context an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the key facts (read-only, free, what it returns), followed by the usage cadence. The inline step list is dense but earns its place by telling the agent what the returned document covers; wording is otherwise tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter documentation tool with no output schema, the description covers the essentials: safety/cost, the exact returned artifact, its subject matter, and when to apply it. Nothing needed to select or invoke the tool is missing.

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 tool takes zero parameters, so there is no parameter meaning to add and the baseline applies. The description correctly spends no space on arguments and instead focuses on scope and return content.

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?

The description uses a specific verb+resource: it returns the setup steps (the text of /setup.md) for adding Klarhimmel UI to a React project, and it enumerates the covered topics (Tailwind, alias, components.json, first block, tokens, design skill). An agent can immediately tell this is a documentation-fetch tool, distinct from the item-oriented siblings get_item and search_items.

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?

The scope condition is explicit: use it for adding Klarhimmel UI to a React project, and "Follow them once per project" tells the agent the intended frequency and that repeating it is unnecessary. It does not name an alternative tool or an explicit when-not-to-use case, which keeps it just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources