Skip to main content
Glama

Add to CRM

Find contact details

find_contact_details
Idempotent

Find a person's work e-mail address, other contact details and current job from their public profile link, an e-mail address, or their name and company. Uses one lookup credit when an e-mail address is found, nothing otherwise.

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": "find_contact_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNothe person's full name; use together with company when there is no profile link or e-mail
emailNoan e-mail address the person is known by
companyNothe company the person works for; use together with name
profile_urlNolink to the person's public profile page (a link with /in/ and the person's handle in it)
include_phoneNoalso look for a mobile number; this uses extra credits and is off unless set

Output Schema

NameRequiredDescriptionDefault
crmNothe name of the customer's connected CRM; absent when none is connected
statusNofound or not_found
contactNo
credits_leftNolookup credits left on the account after this call
credits_usedNolookup credits this call used; 0 when the answer was already stored
phone_lookupNofound, none (looked for, no number exists) or unknown (not looked for)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / contact / properties / emails / items / properties / status / description
      Previous value: -"how sure we are the address is deliverable (verified, likely, unverified, risky)"New value: +"how sure we are the address is deliverable (verified, accept_all, unverified, guessed)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare openWorldHint, idempotent, and non-destructive, so the bar is lower; the description still adds real value by disclosing the credit model ('one lookup credit when an e-mail address is found, nothing otherwise'), which explains why readOnlyHint is false for a pure lookup. It does not state what happens on no-match or whether repeated lookups re-charge.

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?

Two sentences, front-loaded with purpose and immediately followed by the cost condition; no filler or restated title.

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 return values need not be described, and the cost behavior is covered. Minor gaps remain: no statement of behavior when the lookup fails, and no guidance on choosing among the option-dependent sibling tools.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all five parameters including the include_phone cost caveat. The description only restates the input modes at a high level and adds no syntax, format, or precedence rules beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Find') plus the resource and returned fields ('work e-mail address, other contact details and current job'), and enumerates the three accepted input modes (profile link, e-mail, name+company). That distinguishes it in spirit from find_company_details and get_profile, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

The three accepted input modes imply when this tool applies, but there is no explicit routing guidance versus siblings such as find_person_in_crm, get_profile, or search_prospects, nor any stated prerequisite (e.g. needing a profile URL or a name+company pair).

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.