Skip to main content
Glama

Check a business name

check_business_name
Read-onlyIdempotent

Can I use this business name, and is anything stopping me? Check all four areas in one pass: LLC availability, federal trademark conflicts, domains, and social handles. Returns dated verdicts, sources, and the full results URL. Start here for a general business-name availability question. LLC results are preliminary, not reservations; trademark results are a conflict screen, not clearance.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe business, LLC, or trademark name from the conversation. An LLC designator is optional.
tldsNoUp to 30 top-level domains from the conversation. Omit to check com, io, ai, co and net.
statesNoUp to 5 jurisdictions for the LLC name check. Omit when no state was given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / tlds / description
      Previous value: -"Up to 5 top-level domains from the conversation. Omit to check com."New value: +"Up to 30 top-level domains from the conversation. Omit to check com, io, ai, co and net."
    • changedInput schema / properties / tlds / items / enum
      Previous value: -[
      -  "com",
      -  "net",
      -  "org",
      -  "co",
      -  "io",
      -  "us",
      -  "biz"
      -]New value: +[
      +  "com",
      +  "io",
      +  "ai",
      +  "co",
      +  "net",
      +  "org",
      +  "dev",
      +  "app",
      +  "xyz",
      +  "tech",
      +  "us",
      +  "biz",
      +  "info",
      +  "store",
      +  "online",
      +  "site",
      +  "me",
      +  "tv",
      +  "cc",
      +  "cloud",
      +  "agency",
      +  "design",
      +  "studio",
      +  "company",
      +  "solutions",
      +  "world",
      +  "pro",
      +  "shop",
      +  "digital",
      +  "global"
      +]
    • changedInput schema / properties / tlds / maxItems
      Previous value: -5New value: +30
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses what is returned ('dated verdicts, sources, and the full results URL') and two critical caveats: LLC results are preliminary and not reservations, trademark results are a conflict screen not clearance. That is exactly the kind of expectation-setting an agent cannot get from the structured fields.

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?

Front-loaded with the user's underlying question, then the four-area scope, then the return shape, then the disclaimers — a logical order with no filler. Every sentence carries either scope, routing, or a caveat.

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?

No output schema exists, yet the description still characterizes the return (dated verdicts, sources, results URL). Combined with the explicit limitation disclaimers and complete schema coverage, nothing material is missing for a read-only aggregation tool.

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 the schema already fully documents name, tlds, and states, including defaults and max item counts. The description's mention of 'domains' and 'LLC availability' loosely maps to the tlds and states params but adds no format, default, or enumeration detail beyond what the schema supplies.

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+resource ('Check a business name') and immediately enumerates exactly what is checked: LLC availability, federal trademark conflicts, domains, and social handles. The phrase 'all four areas in one pass' distinguishes it from the single-area siblings (check_llc_name, check_domain_availability, check_trademark_conflicts, check_social_handles).

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?

'Start here for a general business-name availability question' gives a clear selection rule that routes the agent to this tool over the narrower siblings. It stops short of explicitly naming those siblings or stating when-not to use it, so it is strong context rather than a full when/when-not/alternatives map.

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