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

Get naming pattern statistics

name_patterns

Read-only

How real products are named: pattern shares with examples, TLDs, domain styles, length and syllables, a per-category table and highlights such as the share of AI tools on .ai. Takes search_names' filters for one slice. Use it before proposing names.

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": "name_patterns"
  }
}

Input Schema

Name	Required	Description
`tld`	No	Comma-separated TLDs (OR).
`length`	No	Letters in the name - a number or a range like 4-6.
`source`	No	library or targets.
`pattern`	No	Comma-separated naming patterns (OR) to summarise.
`category`	No	Comma-separated categories (OR) to summarise, e.g. "AI tools".
`startsWith`	No	Letters the name starts with, or vowel or consonant.

Output Schema

Name	Required	Description	Default
`note`	No
`tlds`	No
`total`	No
`length`	No
`filters`	No
`patterns`	No
`syllables`	No
`byCategory`	No
`highlights`	No
`domainStyles`	No
`startsWithVowel`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 30, 2026
- removedOutput schema / properties / byCategory / items
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / domainStyles / items
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / highlights / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / patterns / items
```
Removed value: -{
-  "type": "object"
-}
```
- removedOutput schema / properties / tlds / items
```
Removed value: -{
-  "type": "object"
-}
```
AddedOct 24, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the bar is lower. The description adds that output is an aggregated summary computed over one filter slice, but most of the rest (TLDs, lengths, category tables, highlights) restates what the output schema likely already enumerates.

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 what is produced, then how filters apply, then when to call. No filler; every clause carries information.

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?

A read-only statistics tool with an output schema and full param coverage needs little more; the description supplies the aggregate-slice framing and pre-naming usage that structured fields don't. Minor gaps (empty-result behavior, filter combination logic) remain.

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 all six params documented, so baseline is 3. The description only adds the cross-tool hint that these are search_names' filters, not individual parameter meaning.

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 subject (naming pattern statistics: pattern shares with examples, TLDs, domain styles, length/syllables, per-category table, highlights) and distinguishes itself from the closest sibling by noting it 'Takes search_names' filters for one slice', implying an aggregate view rather than individual name search.

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?

'Use it before proposing names' gives explicit timing guidance, and the reference to search_names' filters signals the alternative tool for raw names. It lacks an explicit 'not for X' exclusion, but the context is clear enough for selection.

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?