Generect

Find a phone number (most expensive)

find_phone

Find a phone number for one person. Billable: about $0.4 per phone found (a miss is free) at the Tier 0 list price. Accounts can pay a different rate: get_balance returns this account's prices, and every response reports what was actually spent in cost.amount_charged_usd. The most expensive operation here, roughly 20x an email lookup, so it suits people the user has already qualified rather than a whole list. start_bulk_job takes an approved list.

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_phone"
  }
}

Input Schema

Name	Required	Description
`domain`	No	Company domain without protocol, e.g. "stripe.com" (name+domain mode).
`company`	No	Company name or domain (name+company mode).
`lead_id`	No	Generect lead id from search / preview / enrich results: the cheapest and most accurate identifier.
`last_name`	No	Last name (name+domain mode).
`first_name`	No	First name (name+domain mode).
`timeout_ms`	No	Request timeout in milliseconds.
`linkedin_url`	No	LinkedIn profile URL.

Output Schema

Name	Required	Description	Default
`cost`	No
`result`	No
`test_mode`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / lead_id / description

Previous value: -"Generect lead id from search / preview / enrich results — the cheapest and most accurate identifier."New value: +"Generect lead id from search / preview / enrich results: the cheapest and most accurate identifier."

Changed5 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "result": {},
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already disclose openWorldHint=true, destructiveHint=false and a non-readOnly profile, but the description adds genuinely new behavior: billable at about $0.4 per hit with misses free, per-account pricing retrievable via get_balance, and the actual charge surfaced in cost.amount_charged_usd. It stops short of failure modes, timeouts, or rate limits, which keeps it just below the top mark for a spend-incurring tool.

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?

Front-loaded with purpose, then pricing, then the usage decision, so an agent gets the essential facts in the first two sentences. Slight redundancy between the title's 'most expensive' and the body's 'The most expensive operation here' is the only wasted phrasing.

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 an output schema present and full schema coverage, the description need not document return shapes, and it still flags where the cost appears in responses. For a spend-incurring, open-world lookup it covers pricing, scope, and the bulk alternative.

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 explains every one of the seven parameters, including the note that lead_id is the cheapest and most accurate identifier. The description adds no identification-mode guidance itself, so the baseline 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 phone number for one person') and bounds the scope to a single person, which immediately separates it from list-oriented siblings like start_bulk_job. The title's 'most expensive' framing is reinforced in the body rather than left dangling.

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?

Gives explicit when-to-use guidance: it 'suits people the user has already qualified rather than a whole list', and names the alternative for bulk work ('start_bulk_job takes an approved list'). It also gives a comparative cost benchmark (roughly 20x an email lookup) that lets an agent decide between this and a cheaper enrichment path.

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

All Generect tools Inspect

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.