Skip to main content
Glama

List Whitespace Companies

list_whitespace_companies
Read-only

The individual companies one whitespace slice is missing from the CRM: name, website, city, state, country, employees, revenue, the provider's id, whether it is in the ICP, and every attribute the provider sent (fields). Ordered ICP companies first, then by employees and revenue, largest first, so page 1 is the most valuable to add. Use it after get_market_whitespace, passing one of its slice keys and that slice's level; for 'my largest missing ICP companies', use the ICP level's slices. THIS ONE READS THE DATA PROVIDER NOW, a company search, which spends no credits and changes nothing in the CRM. The whole slice is read and matched against the CRM on the first call and kept for ten minutes (provider_read_at, provider_cache_until), so later pages read nothing more; this cache is separate from the stored snapshot get_market_whitespace reads, so its total can differ from the snapshot's. Pages are 100 companies: total_missing, returned, has_more and pages say where you are. complete false means the provider stopped before the end of the slice (a page it refused, or a search too deep to split), so total_missing is a floor and the list is not the whole slice; say so rather than presenting it as the market. Refused (404) for a key the saved TAM no longer has: call get_market_whitespace again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesA slice's key, from get_market_whitespace's levels.<level>.slices.
pageNoPage of 100, from 1. Default 1.
levelNoThe level the slice belongs to. Default tam.
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnly/openWorld/non-destructive, but the description adds substantial extra context: it reads the provider live, spends no credits, changes nothing in the CRM, caches the whole slice for ten minutes (provider_read_at, provider_cache_until), notes the cache is separate from the stored snapshot, and explains complete=false, pagination and 404 behavior.

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?

Front-loads the returned fields and then routes to usage, caching and error handling in a logical order. It is dense and the opening field list is long, but the complexity of caching, pagination and completeness semantics justifies most of the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex, provider-backed, cached, paginated tool with no output schema, the description covers return fields, pagination counters, completeness caveats, cache lifetime and error recovery. Nothing an agent needs to invoke or interpret it correctly appears to be missing.

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 schema documents all four parameters. The description still adds meaning by tying 'key' and 'level' to get_market_whitespace's levels.<level>.slices output, clarifying how to obtain the values rather than just their types.

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 and resource ('the individual companies one whitespace slice is missing from the CRM') and enumerates the exact returned fields. It is clearly distinguishable from siblings like get_market_whitespace and get_persona_whitespace, and even explains its relationship to the former.

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

Usage Guidelines5/5

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

Explicitly says to use it after get_market_whitespace by passing one of its slice keys and the slice's level, and gives a concrete worked case ('my largest missing ICP companies' → use the ICP level's slices). It also supplies the recovery path for a 404 (call get_market_whitespace again).

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.