Skip to main content
Glama

Namepraise

Evaluate a domain name

evaluate_domain
Read-only

Score a domain 0-100 across structure, phonetics, brand, meaning, and market, with a best-effort RDAP availability hint. The score is a brand-quality read, not a price appraisal or a legal opinion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "evaluate_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name or URL to score.
intentNoOptional intended use, sent to the scoring model.
audienceNoBCP-47 language tag.en
includeMarketNoInclude market-fit criteria in the score.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety and network behavior are covered. The description adds that RDAP availability is only a 'best-effort' hint, which usefully sets expectations about reliability, but says nothing about latency, rate limits, or what happens when the RDAP lookup fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the action and scored range, followed by the caveat. Nothing is redundant, though the second sentence mixes output description with usage scoping rather than separating them.

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 no output schema, the description carries the burden of describing returns and does so adequately: a 0-100 score, five named dimensions, and an availability hint. It falls short only on failure modes and whether the score is stable across calls, which matters given idempotentHint=false.

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 parameter (domain, intent, audience, includeMarket) is already documented in the schema, including the note that intent is sent to the scoring model. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 concrete verb and resource with the exact output range and the five scoring axes (structure, phonetics, brand, meaning, market), plus an RDAP availability hint. It also implicitly separates itself from appraisal/legal tools by name, so an agent knows precisely what this produces.

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?

The closing clause explicitly bounds when the output applies: it is a brand-quality read, not a price appraisal or legal opinion. That is a meaningful exclusion, though there is no positive guidance on when to prefer this over other evaluation paths (no siblings exist to route between).

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