Skip to main content
Glama

Enrich people in a batch

enrich_people
Destructive

Use this when the user wants work email addresses or phone numbers for up to 100 people at once. Starts a job and answers with it at once; once the job ends, it lists every person's result in the order they were sent. Name each person one way: by personId, by linkedinUrl, or by a name with companyName or companyDomain. Charged per value found: an email $0.02 from the package or $0.05 from the waterfall, a phone number $0.05 or $0.10. Values a person already had are free. When the job starts, the most it can cost is held from the balance (up to $0.15 a person), and what it does not use is released when it ends. maxSpendUsd is the most this job may cost: $100 unless the user states another amount. Never raise it yourself. A job that could cost more is refused, stating the amount, and nothing is held. Calling again starts a second job.

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": {
      "people": "<people>"
    },
    "name": "enrich_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
findNoWhat to find: a work `email` (the default), a `phone` number, or both (`email_and_phone`).email
peopleYesThe people to enrich, 1 to 100. Name each one way: by `personId`, by `linkedinUrl`, or by a name (`firstName` and `lastName`, or `fullName`) with `companyName` or `companyDomain`.
providersNoWhere to look: `package` (the default) searches our own data package; `waterfall` searches the package, then a fixed series of further providers. A value's price depends on who found it.package
maxSpendUsdNoThe most this job may cost, in US dollars. Leave it out unless the user stated an amount.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations it discloses the asynchronous job lifecycle, result ordering, per-value pricing tiers by provider, that already-known values are free, that a balance hold (up to $0.15/person) is placed and released, and that an over-cap job is refused with the amount stated and nothing held. These are material behaviors for a cost-incurring, non-idempotent call that annotations alone (destructiveHint, idempotentHint=false) could not convey.

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?

The when-to-use clause is front-loaded and each subsequent sentence carries distinct operational information (naming rules, pricing, hold, cap, re-call behavior). It is dense and long, and the pricing sentence is the wordiest part, but nothing is redundant with the schema or annotations.

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 an async, cost-incurring batch tool with no output schema, the definition covers input naming rules, cost bounds, hold/release mechanics, and result ordering. The one ambiguity is how results are retrieved after the job ends ('it lists every person's result') — whether that comes back in this response or requires a later fetch is left implicit.

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 real meaning: maxSpendUsd defaults to $100, should be omitted unless the user states an amount, and must never be raised by the agent. It also explains that price varies by which provider found the value, giving context for the providers enum that the schema only hints at.

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 opens with a specific verb, resource, and scope: 'work email addresses or phone numbers for up to 100 people at once.' That verb+resource+batch-limit combination separates it from the singular enrich_person sibling without needing to name it, and it states the deliverable (emails/phones) rather than just 'enrich'.

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?

It gives a clear trigger ('when the user wants work email addresses or phone numbers ... for up to 100 people at once') and warns that 'calling again starts a second job,' which steers the agent away from accidental duplicate jobs. It does not explicitly point to enrich_person for a single record, so the alternative routing is only implied by the batch scope.

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