Skip to main content
Glama

Search Foundry44 components

search_components

Find animated UI components in the Foundry44 library by what they do (e.g. 'text reveal on scroll', 'cursor glow'). Returns names to pass to get_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
queryNoWords describing the effect, or a component's name.
categoryNoOnly this family.
freeOnlyNoOnly free (MIT) components.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / freeOnly / description
      Previous value: -"Only free (MIT) components, the ones that can be installed today."New value: +"Only free (MIT) components."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does disclose a key behavioral trait — results are names only, not full component payloads, and matching is by described effect rather than exact name. It says nothing about result limits, pagination, or empty-result behavior.

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, zero waste, front-loaded with what it searches and how, followed by what it returns and where to go next.

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 simple three-param search with a fully described schema, the description covers purpose, matching semantics, and return shape. Missing only edge-case behavior (no matches, result caps), which is minor here.

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% and all three parameters (query, category enum, freeOnly) are self-documenting. The description's example phrases ('text reveal on scroll', 'cursor glow') mildly reinforce how to phrase the query but add no new parameter semantics beyond the schema.

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 (find/search) and resource (animated UI components in the Foundry44 library), plus the retrieval key (what the component does, with two concrete examples). It also names the follow-up tool get_component, so the agent can distinguish it from the sibling without opening either schema.

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?

Implies the workflow explicitly: use this to discover, then pass returned names to get_component for details. No explicit exclusions or 'when not to use' guidance, which keeps it from 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