Skip to main content
Glama

Size segments

size_segments
Read-onlyIdempotent

How many businesses each segment has and how many of them have WhatsApp, without listing them. No credits, and doesn't count toward the daily search results. Use it to choose who to target before searching: e.g. for someone who sells espresso machines, compare cafés, bakeries, hotels and restaurants in a place. A segment takes the same filters as search_businesses. Up to 6 segments per call; results come back in the same order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segments": "<segments>"
    },
    "name": "size_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
segmentsYesThe segments to compare

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses two traits an agent would otherwise have to guess: no credit cost and no impact on the daily search quota. It also states batching (max 6 segments) and result ordering, though the 6-segment cap merely restates schema maxItems and the exact return shape (counts only? percentages?) is left implicit.

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 sentences, front-loaded with what it returns and its cost profile before the usage example and the batching/ordering constraints. Every sentence carries distinct information; nothing is restated from the title.

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 filter-heavy aggregation tool with no output schema, the description covers cost, quota, batch size, ordering and filter parity, which is close to everything an agent needs to call it correctly. The one residual gap is the precise shape of each result entry, which the opening sentence only sketches.

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 per-filter meaning is already documented, including the detailed place, booking and category descriptions. The description still adds genuine value with "A segment takes the same filters as search_businesses," telling the agent the filter vocabulary is shared rather than a reduced subset.

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?

"How many businesses each segment has and how many of them have WhatsApp, without listing them" states a specific verb (count) and resource (segments) plus the two metrics returned. The clause "without listing them" plus the reference to search_businesses cleanly separates it from the sibling that returns actual businesses.

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?

"Use it to choose who to target before searching" gives explicit timing and a concrete worked example (espresso machines → cafés, bakeries, hotels, restaurants). It implies the alternative via "before searching" but never states when NOT to use it or what to do if you actually need the business rows.

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