Skip to main content
Glama

Search UI components

search_components
Read-onlyIdempotent

Search the published Dev.cards UI components (hero sections, pricing tables, dashboards, forms, navigation and more) by text and implementation target. Returns compact metadata: id, version, name, category, description and targets. Leave q empty to list every component.

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
qNoText in component id, name, description, category or design brief, e.g. "pricing" or "dashboard".
frameworkNoRequired implementation target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so safety needs no restating. The description adds real behavior the annotations don't cover: exactly which metadata fields come back (id, version, name, category, description, targets) and that an empty query returns the full set, which implies no hidden paging. It doesn't state whether matching is substring or fuzzy, which is the main remaining unknown.

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, zero filler: identity and scope first, return shape second, edge-case behavior third. Every sentence carries information an agent needs to select and call the tool.

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?

With no output schema, the description correctly compensates by listing the returned fields, and it covers the query-omitted case. It falls slightly short on match semantics and on whether framework is effectively required despite the schema's empty required array, both of which an agent would want before calling.

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%, so both q and framework are already documented, and the enum on framework is self-explanatory. The description contributes little beyond the schema except the empty-q semantics, which technically conflicts with the schema's 'Required implementation target' wording for framework. Baseline 3 with a small nudge is fair.

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?

States a specific verb (search) and a specific resource (published Dev.cards UI components), enumerates the category space (hero sections, pricing tables, dashboards, forms, navigation), and scopes the result to compact metadata rather than source. That last clause is what separates it from get_component_code without needing to name the sibling.

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?

The one explicit usage rule is useful: 'Leave q empty to list every component,' i.e. use it as an enumeration tool when there's no keyword. Beyond that there is no when-not guidance and no routing to get_component or get_component_code for full component detail, so the agent must infer that from the 'compact metadata' phrasing.

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