Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bbb_local_bbb

Retrieve a local Better Business Bureau chapter profile from a canonical chapter URL to view office locations, hours, service territory, languages, upcoming events, and news links.

Instructions

Get a local BBB chapter profile. Returns public chapter profile details including office locations and hours, service territory, supported languages, and upcoming public events. news_url is the chapter's constructed newsroom route. When BBB publishes a program tile linking to a recognized newsroom path, published_news_url and its descriptive published_news_title are also returned. Use a canonical chapter URL from bbb-local-bbbs or a business record's local_bbb_url.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical BBB chapter URL from bbb-local-bbbs or a business record's local_bbb_url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full load and does well: it discloses the public nature of the data, the returned sections (hours, territory, languages, events), and the conditional appearance of published_news_url/published_news_title. It stops short of stating auth requirements or pagination, but for a public read tool the disclosure is solid.

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 purpose, then useful return-value detail. The two news_url sentences are slightly verbose but earn their place since no output schema exists to document those conditional fields.

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 single-param tool with no output schema, the description covers both input provenance and return shape, including conditional fields. Remaining gaps (auth, error behavior) are minor for a public profile read.

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 coverage is 100% and the description's URL guidance duplicates the schema's own description verbatim, adding no format or validation detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get') and resource ('local BBB chapter profile'), then enumerates the returned fields. It implicitly separates itself from the sibling bbb_local_bbbs by directing the agent to source the URL from that listing tool rather than duplicating it.

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?

Explains the correct input source ('a canonical chapter URL from bbb-local-bbbs or a business record's local_bbb_url'), which is actionable routing guidance. It does not name an explicit alternative tool or when-not-to-use condition beyond the URL provenance.

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