AlpineLead OI

Start AlpineLead Sales Agent mission

run_sales_mission

Single-tool async Sales Mission state machine.

action=start: starts a mission and returns job_id quickly.
action=status: checks the same job without starting another mission.
action=result: fetches the final result without starting another mission.

This intentionally keeps all async lifecycle operations inside ONE MCP tool so
clients that expose only run_sales_mission can still complete the workflow.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	No	Natural-language sales objective. Required only for action=start.
`tone`	No		professional
`count`	No
`action`	No	Async action: start, status, or result. Use start for a new mission. Use status/result with the returned job_id.	start
`job_id`	No	smj_... job ID returned by a previous start call. Required for action=status or action=result.
`region`	No	Optional region.
`country`	No	Austria, Germany, Switzerland or DACH.	DACH
`district`	No	Optional district.
`industry`	No	Optional target industry.
`language`	No		en
`max_budget`	No	Hard cap in AlpineLead credits. The mission never intentionally exceeds this amount.
`destination`	No	Where to keep/send the result: alpinelead, webhook, pipedrive, hubspot, both, or all.	alpinelead
`referral_id`	No	Optional alr_... ID returned by match_alpinelead_capability.
`minimum_score`	No
`sales_kit_count`	No
`save_to_history`	No
`include_sales_kits`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

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

Changed8 schema fields changedSep 3, 2026

addedInput schema / properties / action

Added value: +{
+  "default": "start",
+  "description": "Async action: start, status, or result. Use start for a new mission. Use status/result with the returned job_id.",
+  "title": "Action",
+  "type": "string"
+}

addedInput schema / properties / goal / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / goal / default
```
Added value: +null
```

changedInput schema / properties / goal / description

Previous value: -"Natural-language sales objective. AlpineLead discovers, qualifies and prioritizes opportunities around this goal."New value: +"Natural-language sales objective. Required only for action=start."

removedInput schema / properties / goal / type
```
Removed value: -"string"
```

addedInput schema / properties / job_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "smj_... job ID returned by a previous start call. Required for action=status or action=result.",
+  "title": "Job Id"
+}

changedInput schema / properties / referral_id / description

Previous value: -"Optional alr_... ID returned by match_alpinelead_capability. Pass it to attribute this mission to the discovery/referral source."New value: +"Optional alr_... ID returned by match_alpinelead_capability."

removedInput schema / required
```
Removed value: -[
-  "goal"
-]
```

Changed1 schema field changedSep 3, 2026

addedInput schema / properties / referral_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional alr_... ID returned by match_alpinelead_capability. Pass it to attribute this mission to the discovery/referral source.",
+  "title": "Referral Id"
+}

Changed1 schema field changedSep 2, 2026
- changedInput schema / properties / language / default
```
Previous value: -"de"New value: +"en"
```

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / destination / description

Previous value: -"Where to keep/send the result: alpinelead, webhook, pipedrive, both, or all."New value: +"Where to keep/send the result: alpinelead, webhook, pipedrive, hubspot, both, or all."

Changed1 schema field changedSep 1, 2026

changedInput schema / properties / destination / description

Previous value: -"Where to keep/send the result: alpinelead, webhook, or both."New value: +"Where to keep/send the result: alpinelead, webhook, pipedrive, both, or all."

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / destination

Added value: +{
+  "default": "alpinelead",
+  "description": "Where to keep/send the result: alpinelead, webhook, or both.",
+  "title": "Destination",
+  "type": "string"
+}

AddedAug 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: it is asynchronous, returns a job_id quickly, and status/result calls are non-starting. It does not contradict the annotations, and it clarifies the state-machine lifecycle that the annotations alone would not convey.

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

Conciseness5/5

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

The description is compact, front-loaded with the core state-machine concept, and uses a short action list plus a one-sentence rationale. Every sentence earns its place with no filler or repetition.

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?

The start/status/result workflow is adequately explained and the output schema covers return-value expectations. It does not mention authentication prerequisites or explicitly route around sibling status/result tools, but for a complex 17-parameter tool with a rich schema the core execution model is clear enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 59% schema coverage and 17 parameters, the description should compensate for the gaps, but it only restates action/job_id semantics already present in the schema. Several parameters (tone, count, language, minimum_score, sales_kit_count, save_to_history, include_sales_kits) remain undocumented in both the schema and the description.

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 clearly states the tool is an async state machine for sales missions and enumerates the start/status/result actions. It conveys a specific verb and resource, but it does not explicitly name or contrast the overlapping sibling tools check_sales_mission_status and get_sales_mission_result, so some sibling differentiation is left implicit.

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

Usage Guidelines4/5

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

It gives explicit per-action guidance: use start for a new mission, status/result for an existing job, and emphasizes that status/result do not start another mission. It does not directly explain when to choose this unified tool over the sibling status/result tools, so it stops short of full alternative routing.

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

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

Need Help?