Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)

Search real product names and their naming patterns

search_names

Read-only

Naming ideas grounded in about 700 real product names, each with domain, TLD, category, naming pattern, length, syllables, casing and domain style (getX.com, Xhq.com…), plus stats for the whole match, e.g. "short invented names for AI tools on .ai". Traits are heuristics; check trademarks and domains before using a new name.

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_names"
  }
}

Input Schema

Name	Required	Description
`q`	No	Words matched against the name, domain, category and the product's own description; any word can match. Ranked by relevance unless sort is given - more matched words first, then a name or category match above a description match, and rarer words above common ones.
`tld`	No	Comma-separated TLDs (OR), e.g. ai,io or .com.
`sort`	No	Order of results - relevance (the default with q), name (the default without q), length or syllables (shortest first).
`limit`	No	Maximum names, 1 to 500.
`length`	No	Letters in the name (spaces and punctuation not counted) - a number or a range like 4-6, -6 or 8-.
`source`	No	library (products Screenrove has captured) or targets (the Mobbin/Refero list).
`dnsHint`	No	Optional and slower - up to 10 candidate domains, comma-separated (e.g. tallyho.com,tallyho.ai), each checked for DNS records over DNS-over-HTTPS. A hint, not a registrar check.
`pattern`	No	Comma-separated naming patterns (OR) - real-word, compound, blend, altered, suffix, prefix, acronym, alphanumeric, person-place, brand-extension, invented.
`category`	No	Comma-separated categories (OR), e.g. "AI tools", "Developer tools" or "finance".
`syllables`	No	Syllables - a number or a range like 1-2.
`startsWith`	No	Letters the name starts with, or vowel or consonant.
`domainStyle`	No	Comma-separated domain styles (OR) - exact, prefixed, suffixed, domain-hack, subdomain, partial, different.

Output Schema

Name	Required	Description	Default
`note`	No
`names`	No
`stats`	No
`total`	No
`dnsHint`	No
`filters`	No
`message`	No
`directory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 31, 2026

addedInput schema / properties / dnsHint

Added value: +{
+  "description": "Optional and slower - up to 10 candidate domains, comma-separated (e.g. tallyho.com,tallyho.ai), each checked for DNS records over DNS-over-HTTPS. A hint, not a registrar check.",
+  "type": "string"
+}

changedInput schema / properties / q / description

Previous value: -"Words matched against the name, domain, category and the product's own description; any word can match, more matches rank first."New value: +"Words matched against the name, domain, category and the product's own description; any word can match. Ranked by relevance unless sort is given - more matched words first, then a name or category match above a description match, and rarer words above common ones."

removedInput schema / properties / sort / default
```
Removed value: -"name"
```

changedInput schema / properties / sort / description

Previous value: -"Order of results - name, length or syllables (shortest first)."New value: +"Order of results - relevance (the default with q), name (the default without q), length or syllables (shortest first)."

changedInput schema / properties / sort / enum

Previous value: -[
-  "name",
-  "length",
-  "syllables"
-]New value: +[
+  "relevance",
+  "name",
+  "length",
+  "syllables"
+]

addedOutput schema / properties / dnsHint
```
Added value: +{
+  "type": "object"
+}
```

Changed6 schema fields changedOct 30, 2026

addedInput schema / properties / limit / maximum
```
Added value: +500
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / q / description

Previous value: -"Words matched against the name, domain and the product's own one-line description."New value: +"Words matched against the name, domain, category and the product's own description; any word can match, more matches rank first."

removedOutput schema / properties / names / items

Removed value: -{
-  "properties": {
-    "casing": {
-      "enum": [
-        "lowercase",
-        "uppercase",
-        "camelcase",
-        "capitalised"
-      ],
-      "type": "string"
-    },
-    "category": {
-      "type": "string"
-    },
-    "collectionUrl": {
-      "type": "string"
-    },
-    "core": {
-      "description": "The part of the name the traits are read from",
-      "type": "string"
-    },
-    "description": {
-      "description": "The product's own meta description",
-      "type": "string"
-    },
-    "domain": {
-      "type": "string"
-    },
-    "domainAffix": {
-      "type": "string"
-    },
-    "domainStyle": {
-      "type": "string"
-    },
-    "length": {
-      "type": "integer"
-    },
-    "name": {
-      "type": "string"
-    },
-    "pattern": {
-      "type": "string"
-    },
-    "patternBy": {
-      "enum": [
-        "heuristic",
-        "override"
-      ],
-      "type": "string"
-    },
-    "patternDetail": {
-      "description": "Parts"
-    },
-    "source": {
-      "enum": [
-        "library",
-        "targets"
-      ],
-      "type": "string"
-    },
-    "startsWithVowel": {
-      "type": "boolean"
-    },
-    "syllables": {
-      "type": "integer"
-    },
-    "tld": {
-      "type": "string"
-    },
-    "words": {
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / stats / description
```
Removed value: -"Patterns"
```

AddedOct 24, 2026

TDQS

A3.8/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, closed-world, non-destructive), and the description adds genuine value on top: the corpus is ~700 names, traits are heuristics rather than facts, trademark/domain checks are the caller's responsibility, and `dnsHint` is flagged as slower. It stops short of describing result pagination or how the aggregate stats are returned.

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 corpus and what it contains, with the caveat placed last where it belongs. The enumeration of available traits is dense but each item earns its place by telling the agent what it can filter or sort on.

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 12 optional parameters, an output schema, and full annotations, the description does the work that remains: corpus size, result shape, the heuristic disclaimer, and the DNS caveat. Only the aggregate-stats behaviour of the response and the zero-query default are left unstated.

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%, so every one of the 12 parameters is already documented, including enum values and range syntax — the baseline of 3 applies. The description contributes only the worked example and the vague 'stats for the whole match', adding little that the schema does not already say.

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?

States a concrete verb and resource ('search real product names'), plus the corpus size (~700 names) and exactly which attributes accompany each result, so an agent knows what a hit looks like. It never names the sibling `name_patterns`, so the boundary between searching names and looking up naming patterns is left to inference.

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 example phrase "short invented names for AI tools on .ai" implicitly demonstrates how a research question maps onto the filters, which is useful but indirect. There is no explicit statement of when to prefer this over `name_patterns`, nor any exclusion or prerequisite beyond the trademark caveat.

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

All Screenrove: UI Design Reference & Screenshots (free Mobbin alternative) tools Inspect

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

Need Help?