Skip to main content
Glama

TryKitt (Unofficial)

Trykitt Find Email

trykitt_find_email
Read-onlyIdempotent

Find a verified work email by full name + company domain (or website URL, TryKitt extracts the domain), via TryKitt.ai. Example: trykitt_find_email({ full_name: "Patrick Collison", domain: "stripe.com", _apiKey: "your-trykitt-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "stripe.com",
      "_apiKey": "your-trykitt-api-key",
      "full_name": "Patrick Collison"
    },
    "name": "trykitt_find_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain or website, e.g. "stripe.com" or "https://stripe.com".
_apiKeyNoYour TryKitt API key (get one at trykitt.ai).
full_nameYesFull name as it appears on LinkedIn or similar, e.g. "Patrick Collison".
linkedin_urlNoOptional LinkedIn profile URL to disambiguate the person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the TryKitt.ai backing service and the fact that it normalizes a URL into a domain. It does not disclose cost/credits, rate limits, or what is returned when no verified email exists.

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?

A single front-loaded sentence carrying the verb, resource, and input modes, followed by a compact call example. Every element earns its place; the example is the only arguable redundancy given the schema already has an examples block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could have said what comes back (an email plus confidence/source, or a not-found result) and whether failures consume credits. For a simple two-required-parameter lookup with full annotation coverage this is not fatal, but the return-value gap leaves it only minimally complete.

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 description coverage is 100%, so all four parameters are already documented in schema, including the optional linkedin_url. The description adds only a small amount of meaning beyond the schema (TryKitt extracts the domain from a URL), which the schema roughly already conveys, so the baseline of 3 applies.

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 ('Find a verified work email') plus the exact inputs needed (full name + company domain) and the provider. An agent can tell immediately what this does and none of the sibling tools overlap with email lookup.

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 description implies the usage context (you have a person's name and employer and want their email) and clarifies that a website URL is acceptable in place of a bare domain. However, it gives no explicit when-not-to-use guidance, no alternatives, and no mention that the optional linkedin_url parameter exists for disambiguation.

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.