Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbb_local_bbbs

List BBB chapters and public offices by country and region code, returning every directory entry for local Better Business Bureau coverage.

Instructions

List local BBB chapters serving a region. Lists every chapter and public office shown on BBB's directory page for a region discovered by bbb-regions. Office addresses can be outside the selected service region.

Input Schema

NameRequiredDescriptionDefault
regionYesTwo-letter region code from bbb-regions
countryYesCountry code from bbb-regions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses a genuinely important behavioral quirk: office addresses can fall outside the selected service region, which prevents misinterpretation of results. It leaves read-only nature implied rather than stated, but the semantic caveat is the more valuable disclosure.

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?

Three short sentences, front-loaded with the core action, followed by scope and the address caveat. The first two sentences overlap somewhat ('List local chapters' vs 'Lists every chapter and public office'), a minor redundancy rather than filler.

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?

For a two-parameter, read-only lookup with no output schema, the description says what is returned (all chapters and public offices) and warns about the address caveat. Nothing essential is missing, though a note on pagination or typical result volume would complete the picture.

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% and both parameters already document their source (bbb-regions) and the country enum. The description reinforces the region provenance but adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 specific verb (List) and resource (local BBB chapters serving a region), and clarifies scope as 'every chapter and public office shown on BBB's directory page'. It implies distinction from bbb_regions (which discovers regions) but never names that sibling, so differentiation is only partial.

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?

Makes the dependency explicit twice: the region is 'discovered by bbb-regions', so the agent knows the input must come from that tool. There is no statement of when NOT to use this tool or of alternative listing tools, but the context is clear enough to route correctly.

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