Skip to main content
Glama

1Network local business directory (read-only)

Count businesses

count_businesses
Read-onlyIdempotent

Count the businesses 1network lists for a category, state and city (or one industry directory). Free and fast. Also tells you where to buy a list of them: lists are sold by Data Candy, never on 1network.

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": "count_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (use with state).
stateNo2-letter state code.
categoryNoCategory slug or name.
directoryNoOne industry directory slug.

Output Schema

NameRequiredDescriptionDefault
countYes
exactYes
filtersYes
data_candyYesWhere to buy a list of these businesses (Data Candy), never on 1network.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 genuinely new behavioral context beyond them: the call is free, it is fast, and the underlying lists can never be purchased through 1network (they are sold by Data Candy), which prevents an agent from promising a purchase path this API does not have.

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, scoping information front-loaded before the commercial note. 'Free and fast' is slightly promotional but carries cost/latency meaning, so little is wasted.

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?

Output schema exists, so return shape needn't be described, and the annotations cover safety. What remains under-specified is the combinatorial rule: zero required parameters means an agent must infer that it supplies either category+state+city or directory alone, which the parenthetical only partly conveys.

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%, so the baseline is 3, but the description adds the one thing the schema cannot: the '(or one industry directory)' alternation, clarifying that directory is an alternative query mode rather than an additional filter. That is real semantic value beyond the field descriptions.

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 and resource (count businesses) plus the exact scoping inputs (category, state, city, or a single industry directory). An agent knows what it returns, though it never contrasts itself with the sibling search_businesses, which is the natural confusion point.

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?

Usage is implied rather than stated: 'Free and fast' hints this is the cheap way to size a market before pulling records, but there is no explicit 'use this when you only need a number, use search_businesses when you need the records'. No exclusions or prerequisites are given.

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