Nombrio Clearance Check

Clearance screen — 2 to 8 names at once (free)

check_names

Read-only

Screen 2-8 candidate names in ONE call and get them ranked by viability (best first). Runs the same live free Clearance Check as check_name for every name in parallel — US trademark verdict, count-only EU trademark screen, domains with prices, social handles, developer namespaces, iOS App Store — and returns a ranked summary, per-name verdicts and full-result links. Use it whenever the user is brainstorming, has a list, or asks which of several names is available or safest — including shortlists of project, package, repo, app or domain names that come up mid-development: one check_names call replaces many check_name calls and finishes in about the time of one. Each name counts as one check against the free fair-use pool (per-caller daily allowance). Not legal advice. Data by nombrio.com.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`names`	Yes	2-8 candidate names, e.g. ["Lumeo", "Brewly", "Northwind"]. Plain names only — no URLs, no TLDs, no @handles. Duplicates are checked once.

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	No
`links`	Yes
`quota`	No	Per-caller fair-use quota. Absent on cache hits and degraded paths.
`checked`	Yes	Names that received a full free-tier answer.
`ranking`	Yes	Names best → worst by viability band; unchecked names last.
`results`	Yes
`summary`	Yes
`requested`	Yes
`disclaimer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 29, 2026

addedOutput schema / properties / results / items / properties / conflicts / items / properties / classLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / verdict / properties / conflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / verdict / properties / euConflictClassLabels

Added value: +{
+  "description": "Human-readable Nice Classification labels ('9 Electronics & Software'), aligned index-for-index with the numeric class array.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedAug 27, 2026

addedOutput schema / properties / results / items / properties / links / properties / apiAccess

Added value: +{
+  "description": "Connect a plan (API key) — checks then run on the caller's own plan quota, independent of the free pools. Present when this check was capped.",
+  "type": "string"
+}

Changed14 schema fields changedAug 23, 2026

changedOutput schema / properties / links / properties / apiAccess / description

Previous value: -"Higher limits for agents/products (request access)."New value: +"Connect your plan for higher limits and EU/UK data."

addedOutput schema / properties / links / properties / apiKeys

Added value: +{
+  "description": "Manage/create API keys to connect a plan.",
+  "type": "string"
+}

addedOutput schema / properties / plan

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checksLimit": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksRemaining": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksUsed": {
+      "type": "integer"
+    },
+    "resetsAt": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / conflicts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "classes": {
+        "items": {
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "owner": {
+        "type": "string"
+      },
+      "registries": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "similarity": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "name",
+      "registries",
+      "similarity"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / results / items / properties / links / properties / report

Added value: +{
+  "description": "Full interactive result on the caller's plan.",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / links / properties / upgrade

Added value: +{
+  "description": "Where to get a plan (pricing).",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / plan

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checksLimit": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksRemaining": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "checksUsed": {
+      "type": "integer"
+    },
+    "resetsAt": {
+      "type": "string"
+    },
+    "tier": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tier"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / registries

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "eu": {
+      "$ref": "#/properties/results/items/properties/registries/properties/us"
+    },
+    "uk": {
+      "$ref": "#/properties/results/items/properties/registries/properties/us"
+    },
+    "us": {
+      "additionalProperties": false,
+      "properties": {
+        "matches": {
+          "type": "integer"
+        },
+        "reason": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "matches"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "us",
+    "eu",
+    "uk"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / results / items / properties / score

Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / source

Added value: +{
+  "enum": [
+    "free",
+    "plan"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / results / items / properties / verdict / properties / confidence / const
```
Removed value: -"low"
```
addedOutput schema / properties / results / items / properties / verdict / properties / confidence / enum
```
Added value: +[
+  "low",
+  "high"
+]
```
changedOutput schema / properties / results / items / properties / verdict / properties / coverage / enum
```
Previous value: -[
-  "US",
-  "US+EU"
-]New value: +[
+  "US",
+  "US+EU",
+  "US+EU+UK"
+]
```

changedOutput schema / properties / results / items / properties / verdict / required

Previous value: -[
-  "coverage",
-  "confidence",
-  "capped"
-]New value: +[
+  "confidence",
+  "capped"
+]

AddedAug 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only and open-world annotations, the description reveals meaningful behavior: parallel execution, the exact data categories screened, the ranked summary/per-name verdicts/link outputs, and the fair-use pool cost per name. The disclaimer 'Not legal advice' and data source 'nombrio.com' add useful context. Nothing contradicts the annotations.

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?

The first sentence is front-loaded with the core action and result, and the rest is information-dense. It is somewhat long as a single paragraph with embedded lists, but every sentence serves a purpose (result, data coverage, usage, cost, disclaimer).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a batched screening tool, the description is complete: it states what data sources are checked, how results are delivered, the per-name pool cost, and the legal caveat. The output schema exists, so not detailing return values is acceptable; only the exact daily allowance is unspecified, but that is dynamic and does not block correct invocation.

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?

The schema already covers 100% of parameter semantics with constraints and examples, so the baseline is 3. The description reinforces that names are candidates and each name is checked, but does not add parameter-level details beyond the schema.

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?

The description opens with a specific verb and resource: 'Screen 2-8 candidate names in ONE call' and states the result ('ranked by viability, best first'). It also distinguishes itself from the sibling check_name by emphasizing the batch (2-8) and parallel execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use it: 'whenever the user is brainstorming, has a list, or asks which of several names is available or safest' and lists mid-development shortlist contexts. It also routes away from the single-name sibling by saying 'one check_names call replaces many check_name calls.'

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

All Nombrio Clearance Check tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?