Skip to main content
Glama

Places By Domain

places_by_domain
Read-onlyIdempotent

List every physical location whose website is on a company domain, the store / office / branch footprint of a business, in the United States and the United Kingdom (Overture Maps places). Give a domain like "starbucks.com" or a full URL; subdomains and paths fold to the registrable domain. Returns the total count, counts by country and by state/region, and the locations with addresses, phones and confidence. Answers "how many locations does acme.com have and where".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "domain": "starbucks.com"
    },
    "name": "places_by_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax locations returned (1-1000, default 100). Counts always cover all matches.
domainYesCompany domain or website URL, e.g. "starbucks.com", "https://www.tesco.com/stores".
regionNoOptional: only locations in this state/region, e.g. "TX".
countryNoOptional: only locations in this country ("US" or "GB").
include_closedNoInclude places Overture marks permanently_closed. Default false.
min_confidenceNoHide places whose Overture existence confidence is below this (0-1). Default 0.7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max locations returned (1–1000, default 100). Counts always cover all matches."New value: +"Max locations returned (1-1000, default 100). Counts always cover all matches."
    • changedInput schema / properties / min_confidence / description
      Previous value: -"Hide places whose Overture existence confidence is below this (0–1). Default 0.7."New value: +"Hide places whose Overture existence confidence is below this (0-1). Default 0.7."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description is free to add substantive behavior: subdomains and paths fold to the registrable domain, closed places are excluded by default, and counts cover all matches regardless of limit. Return payload composition (total, country/region counts, address/phone/confidence records) is also disclosed.

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 scope, then the input form, then the return shape, then the motivating question. It is dense but not padded; the only mild redundancy is restating the output contents that the last sentence already implies.

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 six-parameter, output-schema-less read tool, the description covers the domain normalization, the country coverage, default exclusion of closed places, the independence of counts from limit, and what comes back in each record. An agent has everything needed to invoke it correctly and interpret the result.

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 100%, so the baseline is 3; the description still adds meaning by explaining that any URL path or subdomain is normalized to the registrable domain, which the schema only hints at via examples. The country/region and min_confidence semantics are left entirely to 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?

States a concrete verb and resource ('List every physical location whose website is on a company domain'), scopes it geographically (US and UK) and names the underlying dataset (Overture Maps places). The closing question ('how many locations does acme.com have and where') pins the exact user intent, making it distinguishable from area- or keyword-based place lookups.

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 description gives a clear use context: company footprint enumeration and count-by-geography questions, plus the input form to supply (domain or full URL). It does not name or exclude sibling tools such as places_in_area or places_search, so the agent must infer the boundary itself.

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.