Skip to main content
Glama

Is this business PE-backed?

lookup_business
Read-onlyIdempotent

Checks whether one specific dentist, eye doctor, vet, dermatology or GI practice is private-equity backed, from its name plus city and state or ZIP. A street address or phone number makes the match surer. Also answers for a consumer brand by name or website (e.g. "Orvis" or "orvis.com"), with its owner, backers and sources. Returns a status (match, multiple_matches, possible_matches, no_match, need_location), a "say" sentence in the site's label wording, and matches with label, owner group, backers, PE stake and deal model, confidence, sources (headline, link, date), coverage and a correction link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit ZIP code.
cityNo
nameNoBusiness name as the user or a map listing gives it, e.g. "Aspen Dental" or "Smile Magic of Garland".
phoneNoPhone number in any format.
stateNoTwo-letter state code (TX) or state name.
addressNoStreet address, or a full address like "1476 W Buckingham Rd, Garland, TX 75040".
industryNodental, eye (optometry, ophthalmology, optical), vet, derm, gi, or brand (a consumer brand). Leave out to infer it from the name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / industry / description
      Previous value: -"dental, eye (optometry, ophthalmology, optical), vet, derm or gi. Leave out to infer it from the name."New value: +"dental, eye (optometry, ophthalmology, optical), vet, derm, gi, or brand (a consumer brand). Leave out to infer it from the name."
    • changedInput schema / properties / industry / enum
      Previous value: -[
      -  "dental",
      -  "eye",
      -  "vet",
      -  "derm",
      -  "gi"
      -]New value: +[
      +  "dental",
      +  "eye",
      +  "vet",
      +  "derm",
      +  "gi",
      +  "brand"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is the extra context, and it delivers the full status vocabulary (match, multiple_matches, possible_matches, no_match, need_location) plus a correction link. However, it describes those return values rather than behavior such as which source data is consulted, how fresh it is, or what triggers need_location versus no_match. Solid context but not deep behavioral disclosure beyond 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?

Two sentences, front-loaded with the core question and the identifying inputs, then the secondary brand case and the return payload. The trailing list of return fields is dense but each item is informative; only minor trimming would be possible.

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 and zero required parameters, the description carries the burden of saying what comes back and how little input is needed, and it does both via the status values, the 'say' sentence, and the match fields. The one gap is the absence of any guidance on calling it with nothing, which presumably yields need_location.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the baseline is 3; the description earns a step up by explaining that name plus city/state or ZIP form the minimum identifying set and that address or phone materially improves match confidence. It also covers the brand mode, though it says lookups can be made 'by website' when no website parameter exists, leaving the agent to guess that a domain goes in the name field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: checks whether one specific practice (dental, eye, vet, derm, GI) or consumer brand is private-equity backed, and what comes back. The word 'one specific' implicitly separates it from the discovery-shaped sibling find_businesses, but no sibling is named, so the differentiation is left to inference.

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?

Gives clear usage context: supply a name plus city/state or ZIP, add street address or phone to sharpen the match, or pass a brand name/website for the consumer-brand mode. It never states the exclusion case (e.g. when you only have a category and need to discover businesses first, use find_businesses), so alternatives are unstated.

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