Skip to main content
Glama

Data Candy: US business leads

List industries and categories

list_industries
Read-onlyIdempotent

List the industries you can filter on, with lead counts. Pass search (for example "roof") to also find the more specific categories such as "Roofing contractor". Use the exact names it returns in the industry and category filters. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_industries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum categories to return with search (default 25).
searchNoFind industries and more specific categories containing this text, e.g. "roof".

Output Schema

NameRequiredDescriptionDefault
searchNo
categoriesYes
industriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two things beyond them: results include lead counts, and the call is 'Free' — a meaningful cost signal given credit-purchasing siblings. It says nothing about pagination or result ordering for the no-search case.

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?

Four short sentences, each earning its place: purpose, search behavior with example, downstream instruction, and cost. The most important information (what you get, and the exact-name constraint) is front-loaded with no 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?

An output schema exists, so return values need no explanation, and the description covers the one behavioral question that matters (search widens results to categories). The only gap is how `limit` behaves without `search`, which the schema partially covers.

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%, so both `search` and `limit` are already documented with an example and a default. The description reinforces `search` by explaining that it also returns more specific categories ('roof' → 'Roofing contractor'), which adds real semantic value, but it never mentions `limit`. 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?

Specific verb+resource: lists filterable industries with lead counts, and explains that passing `search` surfaces more specific categories. An agent immediately knows this is a discovery/enumeration tool. It does not explicitly name a sibling it replaces, so a 4 rather than a 5.

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?

The description states the downstream use clearly: 'Use the exact names it returns in the industry and category filters', which tells the agent to call this before filtering tools like preview_leads or quote_leads. It gives no explicit when-not or named alternative, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources