Skip to main content
Glama

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 and UK trademark screens, 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.

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": {
      "names": "<names>"
    },
    "name": "check_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes2-8 candidate names, e.g. ["Lumeo", "Brewly", "Northwind"]. Plain names only — no URLs, no TLDs, no @handles. Duplicates are checked once.

Output Schema

NameRequiredDescriptionDefault
planNo
linksYes
quotaNoPer-caller fair-use quota. Absent on cache hits and degraded paths.
checkedYesNames that received a full free-tier answer.
rankingYesNames best → worst by viability band; unchecked names last.
resultsYes
summaryYes
requestedYes
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
      +}
  2. Changed1 schema field changed
    • 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"
      +}
  3. Changed14 schema fields changed
    • 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"
      +]
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare read-only and open-world, but the description adds material behavior: parallel execution, near-single-call latency, and that each name consumes one check from a per-caller daily free pool. It also discloses the caveat 'Not legal advice' and the data source, which annotations could not convey.

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?

Front-loaded with the core action and its ranking behavior, then usage, then cost. The long em-dash enumeration of screen sources is dense but informative; a slight trim of the coverage list would tighten it without losing selection value.

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?

With an output schema present, the description need not detail return values, and it still summarizes them (ranked summary, per-name verdicts, full-result links). For a one-parameter, read-only batch tool, quota cost, latency, and scope are all covered.

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 coverage is 100% and the single 'names' parameter already documents the 2-8 range, the plain-names restriction, and duplicate handling. The description repeats the 2-8 bound but adds no new syntax or format meaning beyond the schema, so 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 specific verb and resource ('Screen 2-8 candidate names in ONE call') plus the output shape ('ranked by viability, best first'). It explicitly distinguishes itself from the sibling check_name by positioning batch execution as a replacement for many single calls.

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?

Gives concrete triggering conditions: brainstorming, an existing list, or any 'which of several names is available or safest' question, including shortlists arising mid-development. It also names the alternative (repeated check_name calls) and the condition that favors this tool.

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