Skip to main content
Glama

AlpineLead OI

by io.github.maxschnee74-source

RAW DACH company discovery · qualified intent auto-routes

discover_leads

Compatibility RAW discovery. Qualified or ambiguous intent auto-routes to find_opportunities. RAW results require explicit raw wording and internal confirmation, and never contain a final FIT/NEED/NOW opportunity score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesOriginal user request verbatim. REQUIRED. If it contains buyer/need/investment/qualification intent, AlpineLead automatically routes to find_opportunities.
limitNoMaximum result count. Qualified/ambiguous intent is routed to find_opportunities and capped at 5.
regionNoOptional state, province, canton or regional area to narrow the search.
countryNoTarget country or market. Use DACH for Austria, Germany and Switzerland together.DACH
districtNoOptional district, county or local administrative area to narrow the search.
industryYesTarget B2B industry/category. This tool returns RAW candidates only when raw mode is explicitly requested and confirmed.
raw_mode_confirmedNoOptional internal safeguard. Never ask the user for this value. Set true only when the original user request explicitly asks for an unqualified/raw company list; qualified or ambiguous intent auto-routes regardless.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • addedInput schema / properties / raw_mode_confirmed / default
      Added value: +false
    • changedInput schema / properties / raw_mode_confirmed / description
      Previous value: -"REQUIRED explicit confirmation. Set true only when the user explicitly asked for an unqualified/raw company list. This does not bypass automatic routing of qualified intent."New value: +"Optional internal safeguard. Never ask the user for this value. Set true only when the original user request explicitly asks for an unqualified/raw company list; qualified or ambiguous intent auto-routes regardless."
    • changedInput schema / required
      Previous value: -[
-  "industry",
-  "goal",
-  "raw_mode_confirmed"
-]New value: +[
+  "industry",
+  "goal"
+]
  2. Changed5 schema fields changed
    • changedInput schema / properties / goal / description
      Previous value: -"Original user request verbatim. REQUIRED so AlpineLead can distinguish a raw list from buyer/need/investment intent. Qualified intent is automatically routed to find_opportunities and analysis credits apply."New value: +"Original user request verbatim. REQUIRED. If it contains buyer/need/investment/qualification intent, AlpineLead automatically routes to find_opportunities."
    • changedInput schema / properties / industry / description
      Previous value: -"RAW target B2B industry/category. This tool returns candidates, not qualified opportunities."New value: +"Target B2B industry/category. This tool returns RAW candidates only when raw mode is explicitly requested and confirmed."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum result count. For qualified intent this becomes the requested opportunity count, capped at 5."New value: +"Maximum result count. Qualified/ambiguous intent is routed to find_opportunities and capped at 5."
    • addedInput schema / properties / raw_mode_confirmed
      Added value: +{
+  "description": "REQUIRED explicit confirmation. Set true only when the user explicitly asked for an unqualified/raw company list. This does not bypass automatic routing of qualified intent.",
+  "title": "Raw Mode Confirmed",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "industry",
-  "goal"
-]New value: +[
+  "industry",
+  "goal",
+  "raw_mode_confirmed"
+]
  3. Changed4 schema fields changed
    • addedInput schema / properties / goal
      Added value: +{
+  "description": "Original user request verbatim. REQUIRED so AlpineLead can distinguish a raw list from buyer/need/investment intent. Qualified intent is automatically routed to find_opportunities and analysis credits apply.",
+  "title": "Goal",
+  "type": "string"
+}
    • changedInput schema / properties / industry / description
      Previous value: -"Target B2B industry or business category, for example metalworking, construction or logistics."New value: +"RAW target B2B industry/category. This tool returns candidates, not qualified opportunities."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of leads to return."New value: +"Maximum result count. For qualified intent this becomes the requested opportunity count, capped at 5."
    • changedInput schema / required
      Previous value: -[
-  "industry"
-]New value: +[
+  "industry",
+  "goal"
+]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description discloses important behavioral traits beyond the annotations: auto-routing to find_opportunities for qualified/ambiguous intent, the requirement for explicit raw wording and internal confirmation, and the guarantee that RAW results never contain a final FIT/NEED/NOW score. This is substantive and not contradicted by the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and mostly front-loaded, but the opening fragment 'Compatibility RAW discovery.' is cryptic and adds little value. The useful routing and RAW-result constraints are clear, but the acronym-rich wording and unexplained 'Compatibility' reduce clarity.

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 do not need to be described here. The description covers routing conditions, RAW-mode requirements, and the absence of opportunity scores, which is sufficient for correct invocation. Minor gaps like the meaning of 'Compatibility' are not blocking.

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 the schema already documents all parameters. The top-level description mostly restates routing behavior already captured in the goal and raw_mode_confirmed parameter descriptions, adding little new semantic meaning beyond the schema.

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?

The description clearly identifies the tool as RAW company discovery and explicitly distinguishes it from find_opportunities by stating that qualified or ambiguous intent auto-routes there. The title reinforces the DACH scope and RAW nature, so an agent can tell it apart from siblings without inspecting schemas.

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?

The description gives explicit usage guidance: use RAW discovery only when raw wording is explicit and internally confirmed; otherwise qualified or ambiguous intent goes to find_opportunities. This directly tells the agent when to invoke this tool versus the key alternative.

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

All AlpineLead OI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.4/5.0
Disambiguation2/5

Several tools overlap or duplicate: run_sales_mission intentionally duplicates check_sales_mission_status and get_sales_mission_result, and there are multiple capability/routing tools (get_capabilities, match_alpinelead_capability, get_alpinelead_recommendation_packet, recommend_next_tool) with similar purposes. Blank descriptions for several nexus_* tools make their boundaries even harder for an agent to determine.

Naming Consistency2/5

All names use snake_case, but there is no consistent verb_noun pattern. The set mixes prefixed families (agentpub_*, nexus_*, predictive_*_info), noun-only names (winning_pattern, learning_engine), reversed noun_verb names (radar_check, hunter_run), and get/check/run/status variants for closely related operations.

Tool Count1/5

56 tools is far beyond a well-scoped server surface. Many are one-off info, status, or diagnostic tools that could be consolidated into parameterized tools. This places an excessive routing burden on the agent and dilutes the core sales workflow.

Completeness3/5

The core lead-to-CRM workflow is fairly complete: discovery, analysis, qualification, sales kit generation, HubSpot push, and learning/feedback loops are covered. However, there are notable gaps such as no way to list or retrieve saved analyses, no explicit stop/cancel for Hunter or Sales Mission runs, and no update/cancel operations for Nexus tasks.

Resources