Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_bbb_businesses_item

Retrieve a business profile from the BBB businesses dataset by its ID. Returns the matching record or a 404 when it is not indexed.

Instructions

Get a business from the BBB businesses dataset. Returns one business by id from dataset id enum value bbb-businesses. Returns 404 when the business is not in the index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesBusiness id (the <bbbLocalId>-<businessId> slug from the profile URL), e.g. 0825-1000223803

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the dataset enum, the single-item return, and the 404 behavior, which is useful. However, it doesn't disclose response shape, whether data is stale, rate limits, or how the id slug relates to other bbb tools. The 404 mention is the main added behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences, each adding distinct information: operation, dataset scoping, and error behavior. No filler or repetition.

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-parameter lookup tool with no output schema, the description covers the key operational facts: which dataset, what the id looks like, and the 404 behavior. It doesn't describe the return payload structure, but the presence of sibling bbb_business and bbb_business_more_info tools suggests other tools exist for details. It's complete enough for correct invocation.

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% and the description adds the slug format with an example, which complements the schema's description. The dataset enum value in the description also gives context for the id's namespace. The parameter meaning is fully clear.

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?

The description clearly states the tool retrieves a single business from the BBB businesses dataset by id, with a specific dataset enum value. It doesn't explicitly distinguish itself from the sibling bbb_business tool, but the name and dataset-qualified language make the resource clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for retrieving a single business when you already have the id, and mentions a 404 for missing businesses. It doesn't explicitly state when to use this instead of datasets_bbb_businesses_search or bbb_business, so usage context is clear but not contrasted with alternatives.

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