Boomerang

Preview people query

preview_people_query

Read-onlyIdempotent

Preview how many companies and people match a SearchPeopleRequest at each funnel stage (companies -> current employees -> +seniority -> +title keywords -> +person location), without running the final search. Same anchor/filter fields as search_people_by_location_and_seniority. Use this to show the user what each filter is doing before committing to the final query, especially after adding or loosening a filter.

Use when: Use whenever the user is refining a search interactively — after every new filter (region, seniority, title keywords, company set) — to show the funnel counts and let them see which parameter is truncating the result set. Do not use as a substitute for the final search_people_by_location_and_seniority call.

Behavior: read_only, idempotent

Returns stages[] with fields: label company_count people_count by_seniority top_locations top_titles basis sampled_rows

IMPORTANT: If the response contains more than one record, always present the options to the user and ask them to choose before taking any follow-up action. Do not act on all results automatically.

Input Schema

Name	Required	Default
`page`	No
`region`	No
`preview`	No
`last_name`	No
`page_size`	No
`seniority`	No
`first_name`	No
`name_anchor`	No
`company_name`	No
`country_code`	No	US
`workspace_id`	No
`title_persona`	No
`person_regions`	No
`title_keywords`	No
`company_social_id`	No
`per_company_limit`	No
`company_social_ids`	No
`exclude_social_ids`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

removedInput schema / properties / _triggered_by

Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the repeated 'read_only, idempotent' adds nothing; however the description adds real behavioral context with the funnel progression stages and the rule about presenting multiple records to the user before acting. It does not cover pagination/limit behavior, so not a 5.

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-loaded with the core action, then cleanly segmented into Use when / Behavior / Returns / IMPORTANT. Slightly long, and the Returns field enumeration largely duplicates the output schema rather than earning its place.

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 the description need not explain return values (though it does), and annotations carry the safety profile. Intent, usage, funnel semantics and multi-result handling are all covered; only the undocumented non-filter parameters leave a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

18 parameters at 0% schema description coverage, and the description compensates only partially: it names filter dimensions (region, seniority, title keywords, company set) and points to an equivalent sibling schema, but page, page_size, preview, per_company_limit, name_anchor, workspace_id and exclusion params are never explained. Most parameter semantics remain undocumented in both schema and description.

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 ('preview how many companies and people match a SearchPeopleRequest at each funnel stage') and explicitly contrasts it with the final search. The funnel-stage enumeration makes the tool's function unmistakable and distinguishes it from sibling search_people_by_location_and_seniority.

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?

Has an explicit 'Use when' clause naming the interactive-refinement context and an explicit exclusion ('Do not use as a substitute for the final search_people_by_location_and_seniority call'). The alternative and the condition that selects it are both named.

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

All Boomerang tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?