Skip to main content
Glama

Start the guided setup

start_guided_setup
Read-onlyIdempotent

Begin here with a beginner. Returns the four-step path for setting up one bot for one job, the first questions to ask the owner, and the ground rules (one job at a time, draft only, Ask first wins).

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": "start_guided_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoWhat the owner wants help with, in their words.
business_typeNoThe kind of business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine content about what the response contains (four-step path, first questions, ground rules such as draft-only and 'Ask first wins'), which is useful since there is no output schema, but it says nothing about whether the returned path adapts to the supplied goal/business_type.

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?

A single front-loaded sentence that leads with the imperative 'Begin here' and then enumerates the return payload. Dense but every clause adds information; the parenthetical ground-rules list is the only part verging on clutter.

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 usefully summarizes what comes back, and both optional parameters are fully documented in the schema. What is missing is whether inputs shape the returned path and whether the four steps are static or tailored.

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 rich per-parameter descriptions and an enum for business_type, so the schema carries the semantics. The description mentions 'the first questions to ask the owner' but does not tie the goal or business_type inputs to the returned path, so baseline 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?

States a specific action ('Begin here') and names the concrete payload: a four-step path for setting up one bot for one job, plus owner questions and ground rules. It reads clearly as an entry-point tool, distinguished from siblings like get_setup or generate_starter_brief_files by its beginner/onboarding framing, though it never names an alternative outright.

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 opening 'Begin here with a beginner' gives a clear trigger condition — a novice user starting from nothing. It does not state when NOT to use it or point to a specific sibling for advanced cases, so guidance is contextual rather than complete.

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