Skip to main content
Glama

SnoopScan

by com.snoopscan
OverviewDiscussionsAdmin

Find people at a company

people
Read-only

Find the people at a company, by what they do and how senior they are.

Head-hunting a developer, poaching a sales team, or finding who signs the
cheque are the same shape of question: function plus seniority. Give it a
company and optionally a `role` and a `seniority` and it returns named
people from public search — no login, no profile scraping.

role: executive, engineering, product, sales, marketing, finance,
      procurement, talent, operations, data, security, legal, support, design
seniority: exec, vp, director, manager, ic

Each person says whether the employer was CONFIRMED in the source text.
Unconfirmed people are real leads but unproven — the company name did not
appear beside them — and anyone marked former has LEFT. Check those two
flags before you contact anybody.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNo
limitNo
companyYes
seniorityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, the description reveals that results come from public search with 'no login, no profile scraping' and exposes the critical distinction between CONFIRMED and unconfirmed employers, plus a flag for former employees. This is essential behavioral context that is not present in annotations.

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?

The description is structured and front-loaded: purpose first, then examples, parameter enumerations, and finally a safety warning. The role/seniority lists are necessary because the schema lacks enums, and every sentence adds value.

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?

Given an output schema exists, the description covers all key calling requirements: required company, optional role/seniority, allowed values, and the meaning of CONFIRMED/former flags. It also addresses access behavior (no login, no scraping), making it complete for an agent to invoke and interpret results correctly.

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 description coverage is 0%, so the description carries the parameter burden. It enumerates all allowed values for `role` and `seniority`, clarifies their optionality, and implies the company is required. However, it does not explain `limit` beyond the schema's default, leaving one of four parameters under-described.

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?

The description starts with 'Find the people at a company, by what they do and how senior they are' – a specific verb, resource, and scope. It distinguishes this tool from siblings like findContacts/findLeads by emphasizing function-plus-seniority queries and public search with no login.

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 provides clear usage context through relatable examples ('Head-hunting a developer, poaching a sales team...') and explains the input pattern (company plus optional role/seniority). However, it never explicitly names sibling alternatives or states when not to use this tool, so it lacks explicit exclusions.

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

All SnoopScan toolsInspect
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