AlpineLead OI

Find QUALIFIED DACH opportunities · default agent search

find_opportunities

Default agent search: Goal -> Buyer Role -> Buyer Scope -> Need -> Trigger -> Seller Exclusion -> Search Terms -> FIT/NEED/NOW.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	Yes	Original user sales/lead request verbatim. REQUIRED. AlpineLead derives buyer role, buyer scope, need, current trigger and seller exclusions from this context.
`count`	No	Number of qualified opportunities requested.
`region`	No	Optional target state, province or canton.
`country`	No	Austria, Germany, Switzerland or DACH.	DACH
`district`	No	Optional district or local administrative area.
`industry`	No	Optional explicit target buyer industry/company category. If provided, it constrains the buyer scope.
`language`	No	Human-readable opportunity analysis language: de, en, es or fr.	en
`max_credits`	No	Optional hard user credit ceiling. Textual credit caps in goal are also enforced.
`offer_prompt`	No	Optional explicit description of what the user sells. If omitted, goal becomes the semantic Buyer Role / Need / Trigger context and is never null internally.
`minimum_score`	No	Minimum accepted FIT/NEED/NOW opportunity score.
`save_to_history`	No	Save only accepted opportunities to AlpineLead CRM/history.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / max_credits

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 500,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional hard user credit ceiling. Textual credit caps in goal are also enforced.",
+  "title": "Max Credits"
+}

Changed3 schema fields changedSep 5, 2026

changedInput schema / properties / goal / description

Previous value: -"Original user sales/lead request verbatim. REQUIRED. AlpineLead derives buyer role, need, trigger and seller exclusions from this context."New value: +"Original user sales/lead request verbatim. REQUIRED. AlpineLead derives buyer role, buyer scope, need, current trigger and seller exclusions from this context."

changedInput schema / properties / industry / description

Previous value: -"Optional explicit target buyer industry/company category. If provided, it is a hard buyer-scope constraint."New value: +"Optional explicit target buyer industry/company category. If provided, it constrains the buyer scope."

changedInput schema / properties / offer_prompt / description

Previous value: -"Optional explicit description of what the user sells. If omitted, AlpineLead uses goal as semantic Buyer Role / Need / Trigger context; it is never left null internally."New value: +"Optional explicit description of what the user sells. If omitted, goal becomes the semantic Buyer Role / Need / Trigger context and is never null internally."

Changed5 schema fields changedSep 5, 2026

addedInput schema / properties / goal

Added value: +{
+  "description": "Original user sales/lead request verbatim. REQUIRED. AlpineLead derives buyer role, need, trigger and seller exclusions from this context.",
+  "title": "Goal",
+  "type": "string"
+}

changedInput schema / properties / industry / description

Previous value: -"Target industry or company category."New value: +"Optional explicit target buyer industry/company category. If provided, it is a hard buyer-scope constraint."

changedInput schema / properties / minimum_score / description

Previous value: -"Minimum accepted personal/opportunity score."New value: +"Minimum accepted FIT/NEED/NOW opportunity score."

changedInput schema / properties / offer_prompt / description

Previous value: -"What the user sells. Strongly recommended because AlpineLead uses it to judge FIT, NEED and NOW."New value: +"Optional explicit description of what the user sells. If omitted, AlpineLead uses goal as semantic Buyer Role / Need / Trigger context; it is never left null internally."

addedInput schema / required
```
Added value: +[
+  "goal"
+]
```

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "description": "Human-readable opportunity analysis language: de, en, es or fr.",
+  "title": "Language",
+  "type": "string"
+}

First observedAug 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description does not disclose important side effects such as saving accepted opportunities to AlpineLead CRM/history by default, potential credit consumption, or that it is a non-read-only operation. The readOnlyHint=false annotation only signals writes without specifying them.

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 description is extremely concise and free of fluff. However, it is a fragment rather than a complete sentence and relies heavily on the title and schema for meaning.

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

Completeness2/5

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

Given the tool's complexity (11 parameters, scoring, credits, history saving), the description is too thin. It does not explain what the output contains, how FIT/NEED/NOW scores are used, or when to invoke this tool instead of a more specialized sibling.

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% and individual parameter descriptions are fairly detailed, so the baseline is appropriate. The description adds no extra semantic context beyond the schema, especially for how goal and offer_prompt interact.

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?

The name 'find_opportunities' and the phrase 'Default agent search' clearly indicate a search/find operation. The pipeline notation hints at the process, though it does not explicitly say it returns qualified opportunities.

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

Usage Guidelines2/5

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

The description says 'Default agent search' but does not explain when to prefer this tool over related siblings such as discover_leads, analyze_company, or run_sales_mission. No explicit usage conditions or alternative guidance is provided.

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

All AlpineLead OI 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.

Resources

Need Help?