mcp-server-domain-evaluator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| evaluate_brand_qualityB | Grades domain name on pronounceability, memorability, radio test, syllable balance, and visual symmetry. |
| screen_category_vs_trademarkC | Runs heuristic checks to distinguish generic category terms from high-risk corporate trademark violations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target clearly distinct evaluation dimensions: brand quality heuristics versus category/trademark risk screening. There is no apparent overlap in purpose, so an agent can easily select the correct tool.
Both tool names use a consistent snake_case, verb-first convention: evaluate_brand_quality and screen_category_vs_trademark. The pattern is predictable and readable.
Two tools is thin for a domain evaluator, as it likely needs additional checks such as availability, length, TLD suitability, or SEO considerations. The count is borderline rather than clearly appropriate.
The surface covers brand quality and trademark screening but omits other common domain evaluation operations like availability, extension checks, length scoring, or bulk evaluation. These gaps are notable for the stated server purpose.