Skip to main content
Glama
Sign In

Liro

by dev.liro
OverviewDiscussionsAdmin

Search Liro components

search_components
Read-onlyIdempotent

Find Liro React + Tailwind components by what they do. Returns the best matches first with slug, category, access (free or pro) and version. Start here, then call get_component for details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results. Default 8.
queryYesWhat you need, in plain words: "animated dashboard card", "date range picker".
categoryNoOnly this category (name or slug from list_categories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world). The description still adds useful behavior: results are relevance-ranked ("best matches first") and each hit carries slug, category, access tier (free or pro), and version — information an agent needs to decide whether to follow up with get_component.

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 result shape, then the next-step call. Nothing is repeated from the name or schema and no sentence is filler.

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

Completeness3/5

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

Listing the returned fields compensates for the absent output schema, and the follow-up path to get_component is given. However, it says nothing about zero-result behavior or whether pro-only components appear in results despite the access field, which matters for a 3-param discovery tool feeding a paid/free distinction.

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 description coverage is 100%, with plain-language examples for query and a list_categories pointer for category, so the schema does the heavy lifting. The description adds no parameter-level detail beyond framing the search as behavior-based, which is the baseline-3 case.

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 and resource ("Find Liro React + Tailwind components") plus the matching basis ("by what they do"), which cleanly separates it from sibling search_templates and the list_* tools.

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?

Explicitly positions itself as the entry point ("Start here, then call get_component for details") and points to list_categories via the category parameter. It stops short of stating when not to use it (e.g., template lookup belongs to search_templates), so it is clear but not fully disambiguating.

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

All Liro toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources