Skip to main content
Glama

Get a multi-bot crew pack (VIP)

get_multi_bot_crew_pack
Read-onlyIdempotent

VIP. A crew blueprint for one kind of business: a primary bot (Chief of Staff) plus single-job bots, each with a routine and Ask first rules, the routing message for the primary bot, and the order to roll them out. Without a member token it returns the Home Services crew as a labeled demo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_multi_bot_crew_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoThe kind of business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this to be a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is fully covered elsewhere. The description does add genuine behavioral context beyond them: it is VIP-gated, it requires a member token for real output, and it silently degrades to a labeled Home Services demo without one. It does not say what happens to a supplied industry when unauthenticated or how large the payload is.

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?

Two tight sentences with no filler, and the payload contents are described in a single compact clause chain. The leading 'VIP.' fragment is slightly cryptic out of context, but overall the text is well front-loaded and earns its length.

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 single optional enum parameter with full annotation coverage and no output schema, the description says enough about the returned artifact that an agent knows what it will receive. The remaining gap is the interaction between the industry parameter and the missing-token fallback.

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 an enum and per-value description, so the baseline is 3. The description adds only partial meaning beyond the schema, noting the industry selects 'one kind of business,' but it leaves ambiguous whether the industry argument is honored when there is no member token or is overridden by the demo fallback.

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 names the resource precisely and enumerates its contents: a primary bot (Chief of Staff), single-job bots, routines, Ask-first rules, a routing message, and a rollout order. Its only weakness is that the action verb is never stated explicitly (it opens with 'A crew blueprint...' rather than 'Returns...'), and it does not contrast itself against siblings such as get_setup or start_guided_setup.

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: an agent can infer that this is what you call to obtain a multi-bot crew for a business type. The one useful routing hint is that omitting a member token falls back to the Home Services demo, but there is no explicit when-to-use/when-not guidance and no named alternative for related setup work.

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