Skip to main content
Glama

LeanScale GTM Knowledge

search_leanscale

Search everything LeanScale knows: 14 GTM delivery playbooks, 7 proprietary field studies, 151 podcast episodes with operators and executives, 75 customer case studies (anonymized on public keys, named on internal ones), and 117 RevOps docs from www.leanscale.team/knowledge/docs/. The docs explain how to do the work yourself; the playbooks are how LeanScale runs it as an engagement — pass source:"doc" for the first, source:"playbook" for the second. Use this first for any go-to-market, RevOps, sales-ops, marketing-ops, CRM, pipeline, attribution, territory, CPQ, or GTM-tooling question. Returns cited excerpts with source URLs. Also holds the materials from LeanScale's talks, which people ask for by event name: Updata CEO Summit materials: the deck with speaker notes (The Context Graph & Semantic Layer); Updata CEO Summit materials: GTM agents (11 Claude Code plugins for your CRM); Choosing a CRM: migrate off Salesforce, rebuild in place, or stand up a new org; CRM data hygiene and health audit: deduplication, lead status, task hygiene, unused fields and admin permissions; Discovery call structure, mutual action plans and paid vs free pilots; Documenting existing Salesforce flows and automation: inventory, flowcharts per object, and flagging deactivated automation; Which paid advertising channel an early-stage B2B startup should use first; Early-stage outbound: prerequisites, sending domains and deliverability, and what to measure; Founder-led sales to the first sales hire: readiness, profile and why first VP of Sales hires fail; Funnel conversion benchmarks: lead to meeting held to closed-won, win rate and sales cycle; GTM reporting readiness checklist: can your CRM measure conversion, velocity, churn, ARR and revenue recognition?; Lead-to-account matching: approaches, match keys and what goes wrong; Lifecycle stage timestamps and recycled MQLs: never regress the stage, re-enter with dated fields; Marketing nurture email: sending from a subdomain vs a separate domain, and protecting deliverability; New account executive ramp plan: 30-60-90 milestones, certification, call shadowing and deal reviews; Separate pipelines for new business, renewal and expansion: deal types, renewal creation and pilots; Partner program operations: PRM implementation, deal registration and cloud marketplace co-sell; Pipeline stage definitions, exit criteria and required fields per stage; How to build pipeline when cold outreach stops working; Selling into a limited TAM: fintech go-to-market for banks and credit unions; Speed to lead: definition, start and end timestamps, business hours, and median vs average; Updata CEO Summit materials: metric definitions worksheet (40 GTM definitions); Updata CEO Summit materials — The Context Graph & Semantic Layer. Pass source:"resource" to search only those.

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": {
      "query": "<query>"
    },
    "name": "search_leanscale"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many excerpts to return (default 6).
queryYesWhat you want to know. Natural language works better than keywords.
sourceNoRestrict to one kind of source. Defaults to searching everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "playbook",
      -  "study",
      -  "podcast",
      -  "case_study",
      -  "doc",
      -  "any"
      -]New value: +[
      +  "playbook",
      +  "study",
      +  "podcast",
      +  "case_study",
      +  "doc",
      +  "resource",
      +  "any"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses that results are cited excerpts with source URLs and that case studies are anonymized on public keys but named on internal ones — genuinely useful access context. It says nothing about ranking/relevance behavior, result size beyond the default, or failure modes when a source has no matches.

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

Conciseness2/5

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

The purpose and source-routing guidance are front-loaded and tight, but roughly half the text is a 30-item dump of talk and deck titles that reads as a content catalog rather than tool-selection guidance. That bulk dilutes the actionable instructions and makes the description far longer than needed to call the tool correctly.

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?

With no output schema and no annotations, the description does the necessary work: it defines the indexed corpus, the source partitioning, the return shape (cited excerpts with URLs), and a priority rule for use. Only relevance behavior and empty-result handling are unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the enum by explaining the doc-vs-playbook distinction (self-serve docs vs how LeanScale runs the engagement) and what source:"resource" isolates. The limit parameter's default and range are left entirely to the schema.

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?

States a specific verb ("Search") and an enumerated corpus (playbooks, field studies, podcast episodes, case studies, docs) with counts, so the agent knows exactly what is indexed. It does not name siblings like search_podcast or get_playbook, though the source-filter explanation implicitly routes to those narrower sources.

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?

"Use this first for any go-to-market, RevOps, sales-ops, marketing-ops, CRM, pipeline... question" gives a clear positive trigger and priority ordering. It lacks explicit when-not-to-use guidance or named alternatives, leaving the agent to infer that narrower sibling tools exist for single-source lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources