Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_bbb_scamtracker_reports_item

Get a report from the BBB Scam Tracker reports dataset. Returns one stored report by id from dataset id enum value bbb-scamtracker-reports.

Instructions

Get a report from the BBB Scam Tracker reports dataset. Returns one stored report by id from dataset id enum value bbb-scamtracker-reports. Returns 404 when the report is not in the archive; the live bbb-scamtracker-detail endpoint can still fetch it from BBB.

Input Schema

NameRequiredDescriptionDefault
idYesBBB Scam Tracker report id (numeric), e.g. 1397968

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?

No annotations are provided, so the description carries the full behavioral burden and does so well: it discloses that only stored/archived reports are returned, that a 404 signals absence from the archive, and that a live fallback exists. It does not cover auth or rate limits, but the key behavioral traits for a read-by-id tool are present.

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 purpose, then the archive/404 behavior and fallback. The dataset-id enum mention is slightly redundant for this tool but costs little.

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 one-parameter read tool with no output schema, the description states what is returned (one stored report), the archive limitation, and the failure/fallback path. An agent has enough to invoke it correctly, though a bit more on return shape could help.

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 the single id parameter is fully documented in the schema, so the baseline is 3. The description adds no syntax or format detail for id beyond what the schema already provides; the dataset enum reference is not a parameter of this tool.

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 (a report from the BBB Scam Tracker reports dataset), and clarifies it returns one stored report by id. This cleanly distinguishes it from the sibling search/facets tools and from the live bbb_scamtracker_detail endpoint.

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?

Gives explicit routing guidance for the failure case: when the report is not in the archive (404), the live bbb_scamtracker-detail endpoint can still fetch it. It does not spell out the broader 'use this when you already have an id' condition, but the retrieve-vs-search distinction is clear from the siblings.

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