Skip to main content
Glama

Find a DIYA component

search_components
Read-onlyIdempotent

Find the DIYA components or patterns for a job, in plain words ("toggle for email alerts", "settings form", "empty table"). Returns names, imports and when to use each.

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 to return; 5 if left out
queryYesWhat the UI needs to do

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare a safe, idempotent, closed-world read, so the description doesn't need to argue safety. It earns credit for disclosing the response payload — "names, imports and when to use each" — which is real behavioral information absent from any output schema.

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?

Two sentences, front-loaded with the purpose and immediately followed by concrete query examples and the return shape. No sentence is redundant and nothing important is buried.

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 two-parameter read-only search with no output schema, the definition covers what it does, how to phrase input, and what comes back. Only edge behavior (empty results, whether patterns and components are mixed in ranking) is unaddressed, which is minor at this complexity.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema doesn't: the query parameter is meant to take natural-language task phrasing, illustrated by three worked examples. That materially shapes how an agent formulates the required argument. The limit parameter's maximum/default is left entirely to the schema.

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

Purpose4/5

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

"Find the DIYA components or patterns" pairs a specific verb with a specific resource, and the natural-language query examples ("toggle for email alerts", "settings form") make the discovery intent unmistakable versus a by-name lookup like get_component. It never names the sibling tool explicitly, so the differentiation is implied rather than stated.

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 description conveys the usage mode well — search by describing what the UI needs to do, in plain words — and shows three concrete query shapes. It stops short of stating when to prefer this over get_component (e.g., once you already know a name) or what happens if no match is found, so guidance is implied rather than explicit.

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