Browse curated SwiftUI components with metadata and optional category filtering to locate a component before fetching its source code.
List curated SwiftUI components (id, title, category, description, minIOS, tags). Optionally filter by category. Use get_component to fetch the full source for one.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional category filter (exact match, see list_categories). |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden of disclosing behavior. It mentions the output fields and the optional filter, but does not disclose potential side effects (none expected), pagination, or default sorting. For a simple read-only list, this is adequate but lacks depth on edge cases like empty results or performance.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences. The first states the core purpose and output fields, the second points to the sibling for full source. No filler, and the key information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional parameter and no output schema, the description covers the essential aspects: what it returns, the filter, and the alternative for full source. It lacks details on sorting or pagination, but those are not critical for a basic list operation. An agent can invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description repeats the category filter but adds no new information beyond the schema, which already notes exact match and references list_categories. The description does not enhance parameter understanding beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists curated SwiftUI components and specifies the fields returned. It differentiates itself from get_component by noting that tool fetches the full source, but it does not explicitly distinguish from search_components or list_categories, leaving some ambiguity about when to choose this over search_components.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit guidance to use get_component for full source, and mentions the optional category filter. However, it does not mention search_components as an alternative for searching, so the when-to-use context is incomplete but not misleading.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.