search_interfacesUse to discover public liked Gravity AI UI interface drafts by title, summary, or id. This returns public gallery metadata only. Use get_interface when you need the full payload or React code for a known id.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional maximum result count. Defaults to 10 and is clamped to 1-48. | |
| query | No | Optional text matched against public interface titles and summaries. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's job is lighter. It adds context by stating 'This returns public gallery metadata only,' clarifying the output scope and the limitation that it does not return full payloads or React code. This goes beyond the annotations without contradicting them.
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 three sentences, front-loaded with the primary purpose, and each sentence earns its place. It is concise, clear, and includes a useful pointer to a sibling tool without unnecessary detail.
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?
Given the tool has only two optional parameters, no output schema, and rich annotations, the description is complete. It explains what the tool searches, what it returns, and when to use an alternative. The absence of return format details is acceptable for a search tool.
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 adds 'or id' to the search fields, but the schema says 'query' is matched against titles and summaries only, which introduces ambiguity. It does not significantly elaborate on the 'limit' parameter beyond what the schema states.
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's purpose: 'discover public liked Gravity AI UI interface drafts by title, summary, or id.' It uses a specific verb (discover/search), identifies the resource (public liked UI interface drafts), and distinguishes itself from get_interface by noting it returns metadata only.
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 explicitly provides usage guidance by stating 'Use get_interface when you need the full payload or React code for a known id.' This clearly differentiates when to use this tool versus an alternative, and implies this tool is for discovery/search rather than retrieval.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: generate creates new interfaces, get fetches by specific id, refine modifies existing payloads, and search discovers by keywords. No two tools have overlapping boundaries, making it easy for an agent to select the right one.
All tools follow a verb_noun pattern with underscores (generate_interface, get_interface, refine_interface, search_interfaces). The only minor deviation is the pluralization of 'interfaces' in search_interfaces, which is a common exception for discovery operations and does not hinder readability.
With only 4 tools, the server is tightly scoped for the domain of Gravity AI UI generation and retrieval. Each tool serves a necessary role without redundancy or bloat, fitting well within the ideal range.
The tool surface covers the complete lifecycle for a design generation service: create, read, update, and discover. While there is no explicit delete or publish, those actions are intentionally excluded per the descriptions, so there are no dead ends for typical workflows.