Skip to main content
Glama
Sign In
Panda Federation Tools

Panda Federation Tools

by pandadad0214
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Local Business Leads: Google Maps Alternative (OpenStreetMap)

local_business_leads
Read-only

Find local businesses by category and city, such as dentists in Tempe, AZ, with address, phone, email, website, hours, and social links from OpenStreetMap; export results to Excel or CSV.

Instructions

Use this to list local businesses by category and city, e.g. dentists in Tempe AZ. Output: one row per business with address, phone, email, website, opening hours and socials from OpenStreetMap (open license), plus Excel and CSV.

Runs the Apify Actor pandadad0214/local-business-leads (https://apify.com/pandadad0214/local-business-leads) on your own Apify account. Price: $0.001 per business found. Runs that find nothing are not charged per result. Spending is capped per call by run_max_charge_usd.

Input Schema

NameRequiredDescriptionDefault
sortByNoSort by. Most complete = businesses with phone, email, website, address and hours first. Name = A to Z. Choices: mostComplete = Most complete contact details first; name = Name (A-Z).mostComplete
latitudeNoLatitude. Optional. Instead of a location name: center latitude, e.g. 33.4255 (used with longitude and radius; radius defaults to 5 km).
locationNoLocation. City, county, state, ZIP or neighborhood, e.g. "Tempe, Arizona", "Austin, TX", "London", "90210". Smaller areas are faster; whole US states or countries may time out (use a radius or a city).
radiusKmNoRadius (km). Optional. Search a circle of this many km around the location's center instead of its official boundary. 1 to 100.
longitudeNoLongitude. Optional. Center longitude, e.g. -111.9400.
categoriesNoBusiness categories. Plain words, one per line: dentist, plumber, restaurant, coffee shop, lawyer, hair salon, gym, real estate, car repair… (about 150 built in). Other words are matched against OpenStreetMap tags and names. Power users can enter a tag like shop=florist or craft=hvac.
maxResultsNoMaximum businesses. You pay per returned business, so this also caps the cost. Whole number, 1 to 10,000; default 200.
requireEmailNoOnly businesses with an email. Keep only businesses that list an email address (fewer results: most businesses publish phone and website, fewer publish email).
requirePhoneNoOnly businesses with a phone number. Keep only businesses that list a phone number.
run_max_itemsNoOptional. Most results to return from this call (default from PANDA_MAX_ITEMS, 50). Also limits how many results the Actor produces and charges for, unless you set its own max field.
requireWebsiteNoOnly businesses with a website. Keep only businesses that list a website on OpenStreetMap.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the billing model ($0.001 per business found), that empty runs are not charged per result, the per-call spending cap via run_max_charge_usd, and that it executes a named Apify Actor on the user's own account. That is exactly the cost/auth/execution context an agent cannot infer from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what it does and what it returns, followed by a compact execution/pricing paragraph; every sentence carries information. The pricing and charge-cap sentence slightly overlaps the run_max_charge_usd schema text, which is the only redundancy.

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 13-parameter, no-required-input tool with no output schema, the description supplies both the invocation gist and the return shape (one row per business with address, phone, email, website, hours, socials, plus Excel/CSV). Combined with annotations covering safety and open-world behavior, nothing essential is missing.

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 every parameter is already documented in detail (including enums, ranges, and defaults), which sets the baseline at 3. The description only lightly reinforces cost control through run_max_charge_usd and adds no meaning about parameters the schema does not already cover.

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 ('list local businesses by category and city') with a concrete example ('dentists in Tempe AZ'), and names the data source (OpenStreetMap) so an agent can tell it apart from vertical lead tools like trucking_company_leads or podcast_leads_finder without opening the schema.

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?

'Use this to list local businesses by category and city' gives a clear use case with an example query shape. It lacks any explicit exclusion or routing statement (e.g. when to prefer a sibling lead-finder over this one), so it stops short of the 5 bar.

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

Deploy Server

Other Tools