Skip to main content
Glama

Enrich a person

enrich_person
Destructive

Use this when the user wants one person's work email address, phone number or both. Name the person one way: by personId, by linkedinUrl, or by a name with companyName or companyDomain. find says what to look for (an email by default); providers says where: package (the default) searches our own data, and waterfall goes on to further providers, which can take over a minute. The person is saved in the workspace with what was found. 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. A search that finds nothing is free. Personal email addresses are never returned or charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enrich_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
findNoWhat to find: a work `email` (the default), a `phone` number, or both (`email_and_phone`).email
fullNameNoThe person's full name, in place of `firstName` and `lastName`, with `companyName` or `companyDomain`.
lastNameNoThe person's last name, with `companyName` or `companyDomain`.
personIdNoThe person's id: the `id` of their row on a list, or the id an earlier enrichment or upload answered. Send it on its own.
firstNameNoThe person's first name, 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
companyNameNoThe name of the company the person works at.
linkedinUrlNoThe person's LinkedIn profile URL. Send it on its own.
companyDomainNoThe website domain of the company the person works at, such as `northwind.example`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing cost per value ($0.02/$0.05 for email, $0.05/$0.10 for phone), that already-known values and empty searches are free, that personal emails are never returned or charged, and that the person is persisted to the workspace. That persistence detail is the key behavioral fact the agent needs alongside destructiveHint=true. It stops short of saying whether existing field values can be overwritten.

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?

Front-loads the trigger and the identity rule before the pricing block, so an agent can act on the first two sentences alone. Dense but every sentence carries actionable information (identity mode, provider latency, cost, privacy); nothing is decorative padding.

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?

With 9 parameters, no output schema, and mutation annotations, this is the right amount of coverage: trigger, identity modes, provider choice with latency, cost model, and privacy rules. Since there is no output schema, the description's note about what gets saved compensates adequately.

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. The description adds real meaning beyond the schema: it frames the identity parameters as mutually exclusive alternatives ("Name the person one way") and restates the defaults for find and providers in context rather than in isolation.

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 (enrich one person) plus the exact outputs (work email, phone, or both). The phrase "one person" distinguishes it from the plural sibling enrich_people without needing to open either schema.

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?

Opens with an explicit trigger ("Use this when the user wants one person's work email..."). It then constrains identity input to exactly one of three modes (personId, linkedinUrl, or a name with companyName/companyDomain) and explains the package-vs-waterfall tradeoff, including that waterfall "can take over a minute".

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