AlpineLead OI

Generate sales kit

generate_sales_kit

Use after a prospect has been analyzed and is worth contacting. Generates structured, outreach-ready sales context.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>",
      "website": "<website>"
    },
    "name": "generate_sales_kit"
  }
}

Input Schema

Name	Required	Description	Default
`tone`	No	Desired outreach tone, for example professional, concise, consultative or friendly.	professional
`website`	Yes	Company website URL used as context for the sales kit.
`language`	No	Output language: de, en, es or fr. Defaults to English for international agent workflows.	en
`company_name`	Yes	Company name for which the sales kit should be generated.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

changedInput schema / properties / language / default
```
Previous value: -"de"New value: +"en"
```

changedInput schema / properties / language / description

Previous value: -"Output language code, for example de for German or en for English."New value: +"Output language: de, en, es or fr. Defaults to English for international agent workflows."

First observedAug 23, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations indicate readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the tool may have side effects, but the description does not disclose what those could be (e.g., external calls, data persistence). The description adds the context of generating outreach-ready material, but does not clarify side effects or permissions. No contradiction with annotations, but limited behavioral disclosure.

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 two sentences with no filler. The usage condition is front-loaded, and the purpose is stated directly. It earns its place by providing both when-to-use and what-it-does without redundancy.

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

Completeness3/5

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

Given the presence of an output schema and 100% parameter documentation, the description does not need to explain return values. However, it lacks details about side effects or costs (e.g., credit consumption), and does not mention any limitations or prerequisites beyond 'prospect analyzed.' For a tool that may write or trigger external actions (openWorldHint=true), slightly more contextual guidance would improve completeness.

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 fully documents each parameter. The description does not add additional semantic meaning beyond the schema, which is acceptable given the high coverage, but it also does not provide any extra context such as how website or company_name affect the output. Baseline 3 is appropriate.

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?

Description clearly states a specific verb and resource: 'Generates structured, outreach-ready sales context.' It distinguishes itself by specifying the prerequisite (post-analysis prospect), which differentiates it from sibling tools like analyze_company or run_sales_mission, though it does not explicitly name an alternative.

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?

The description gives explicit temporal guidance: 'Use after a prospect has been analyzed and is worth contacting.' This is a clear context, but it does not state when not to use the tool or mention any alternative tools, leaving room for more explicit exclusionary guidance.

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?