Skip to main content
Glama
Sign In
Mach GTM MCP

Mach GTM MCP

by verma6uc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

build_icp

Define an outbound prospecting ICP from your company details and best customers, returning firmographics, technographics, pain points, buying signals, and proof points.

Instructions

Define an Ideal Customer Profile (ICP) for outbound prospecting. Returns a structured ICP with firmographics, technographics, pain points, buying signals and proof points — ready to use in Mach GTM.

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_description": "<company_description>",
      "best_customers": "<best_customers>"
    },
    "name": "build_icp"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_sizeNoTypical deal size / ACV (e.g. "$20k-$50k ACV")
best_customersYesDescribe your best 2-3 existing customers — industry, size, role, what problem you solved.
company_descriptionYesWhat your company does and what you sell (1-3 sentences).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden here and partially meets it by enumerating the returned ICP components (firmographics, technographics, pain points, buying signals, proof points). It says nothing about how the profile is generated, whether it is persisted or re-definable, latency/cost, or what happens with sparse inputs — meaningful gaps for a generation tool with zero annotation coverage.

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?

Two sentences, zero filler, with the purpose front-loaded and the return contents immediately following. Nothing could be removed without losing information.

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?

For a three-parameter, no-output-schema tool, the description supplies the missing return contract and states the domain. What remains absent — persistence, iteration, and downstream ordering — is minor but real given the complete lack of annotations.

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 coverage is 100% and each of the three parameters has a self-explanatory description, so the schema does the heavy lifting. The description adds no extra meaning about how inputs influence the generated ICP (e.g. whether deal_size is optional or how best_customers shapes the output), so the baseline of 3 applies.

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 gives a specific verb and resource: 'Define an Ideal Customer Profile (ICP) for outbound prospecting', immediately distinguishing it from write-oriented siblings like draft_outreach or build_sequence. It does not explicitly name a sibling tool or contrast itself with one, so it stops short of a 5.

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?

Usage is only implied: 'for outbound prospecting' and 'ready to use in Mach GTM' suggest this is a setup step whose output feeds later tools, but there is no explicit when-to-use, no ordering guidance (e.g. run before build_sequence), and no stated prerequisites or exclusions.

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

Deploy Server

Other Tools