Skip to main content
Glama

AlpineLead OI

by io.github.maxschnee74-source

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
NameRequiredDescriptionDefault
goalYesOriginal user sales/lead request verbatim. REQUIRED. AlpineLead derives buyer role, buyer scope, need, current trigger and seller exclusions from this context.
countNoNumber of qualified opportunities requested.
regionNoOptional target state, province or canton.
countryNoAustria, Germany, Switzerland or DACH.DACH
districtNoOptional district or local administrative area.
industryNoOptional explicit target buyer industry/company category. If provided, it constrains the buyer scope.
languageNoHuman-readable opportunity analysis language: de, en, es or fr.en
offer_promptNoOptional explicit description of what the user sells. If omitted, goal becomes the semantic Buyer Role / Need / Trigger context and is never null internally.
minimum_scoreNoMinimum accepted FIT/NEED/NOW opportunity score.
save_to_historyNoSave only accepted opportunities to AlpineLead CRM/history.

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
    • 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."
  2. Changed5 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "default": "en",
+  "description": "Human-readable opportunity analysis language: de, en, es or fr.",
+  "title": "Language",
+  "type": "string"
+}
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate the tool is not read-only, not idempotent, and not destructive, which conflicts with the description's implication of a search operation that saves to history. The description adds context that it saves only accepted opportunities to AlpineLead CRM/history (also visible in schema), and the search pipeline shape, but it doesn't disclose side effects beyond save_to_history. No contradiction with annotations; the description and annotations align on non-read-only due to saving.

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 compact and front-loaded: it states the tool's role in the first phrase and then lists the search pipeline as a memorable sequence. It earns its place by encoding the tool's logic into a compact mnemonic.

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?

Given the output schema exists and annotations are present, the description is reasonably complete for an agent. It explains the overall workflow, mentions saving behavior, and the schema covers parameters. However, it doesn't explicitly specify return format, but output schema covers that. It could state when not to use it (e.g., for raw lead discovery vs. qualified opportunities), but the title and description strongly imply the target use case.

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 documents all 10 parameters. The description adds the semantic pipeline concept (Goal -> Buyer Role -> ...) and clarifies that goal is the primary context, which adds meaning beyond the schema. It doesn't need to repeat parameter details because the schema is comprehensive.

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 description states a specific process for finding qualified DACH opportunities, with a clear resource ('default agent search') and a structured sequence of criteria. It distinguishes itself from siblings like discover_leads or run_dach_company_research_agent, though it doesn't name them 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 description implies it is the default agent search for qualified DACH opportunities and outlines the search pipeline, but it does not explicitly state when to use this tool versus alternatives such as discover_leads or run_dach_company_research_agent. The title adds 'default agent search', which suggests primary usage, but no exclusions or explicit alternative routing are 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 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