Skip to main content
Glama

Build Your Stack

build_stack
Read-only

Build Your Stack from The Stack Index. Takes revenue band, motion, binding constraint and budget posture, and returns install order by layer: install first, install next, not yet. Every tool comes with the operators who run it, and the result includes a build_url that opens the same build on pro.gtmvault.co. Use for tool or stack recommendations.

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": {
      "revenue_band": "<revenue_band>",
      "motion": "<motion>",
      "binding_constraint": "<binding_constraint>",
      "budget_posture": "<budget_posture>"
    },
    "name": "build_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
motionYesplg: product-led, self-serve. smb: sales-led, SMB and mid-market. ent: enterprise and ABM. hybrid: product-led plus sales.
revenue_bandYespre: pre-PMF, under $2M ARR. a: $2M to $20M ARR. b: $20M to $100M ARR. c: $100M+ ARR.
budget_postureYesfree: self-serve only, card on file. mid: mid-market, annual contracts. ent: enterprise, negotiated.
binding_constraintYesnopipe: there is no pipeline. noconvert: pipeline does not convert. forecast: the forecast is wrong. cac: CAC is rising. scale: headcount is outrunning the system.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them — the layered install-first/next/not-yet output, that each recommendation carries the operators who run the tool, and that a build_url deep-links to the same build on pro.gtmvault.co. It does not discuss determinism or whether results vary between calls, which keeps it off a 5.

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?

Four short sentences, front-loaded with the action and output structure, and the trailing 'Use for...' sentence is a useful pointer rather than filler. The opening clause naming the index is mildly redundant with the name/title, but nothing else is wasted.

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, the description correctly carries the return-value burden by explaining the three install tiers, the embedded operator data, and the build_url. For a four-required-enum tool it is close to sufficient; only the absence of any note on how conflicting inputs are resolved is a small gap.

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% with detailed per-enum meanings (revenue bands, motions, constraints, budget postures), so the schema already does the heavy lifting. The description only restates the four parameter names, adding no semantics about how they interact or which combination drives which output layer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Build Your Stack from The Stack Index'), names the four inputs it consumes, and describes the output shape (install order by layer: install first, install next, not yet). An agent can distinguish this recommendation-builder from the list_/get_ siblings without opening any schema.

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 closing sentence 'Use for tool or stack recommendations' gives a general usage context but names no conditions, prerequisites, or alternatives. It does not tell the agent when a playbook lookup (get_playbook) or layer audit (run_layer_audit) would be the better call, leaving selection to inference.

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