Skip to main content
Glama

Setup script: what to ask the owner, step by step

dosai_get_setup_guide
Read-onlyIdempotent

CALL THIS FIRST when the owner asks to set up, configure, finish or improve the bot ("настрой бота", "set everything up", "что ещё включить", "чего не хватает"). Returns the interview script built from the project's real state: 15 stages (description, hours, prices and knowledge, channel, notifications, functions, tags and funnel, follow-ups, booking reminders, reports, keyword replies, integrations, balance, test, gaps), each with status (done, todo, offer), why the business needs it, the questions to ask and the tools to use. Follow rules, go stage by stage, call it again after every few stages. Without project_id: lists the projects and says how to start.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say read-only/idempotent; the description goes well beyond by disclosing the return structure (15 stages, each with status done/todo/offer, rationale, questions, and tools) and the re-invocation pattern needed as stages complete. Since there is no output schema, this disclosure is the only source for what the agent will receive.

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?

Front-loaded with the action cue and trigger phrases, then stages, then workflow, then the no-param fallback — a sensible order with no filler sentences. The long parenthetical listing all 15 stages is dense but functionally useful; it could be trimmed slightly without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter read tool with no output schema, everything an agent needs is present: when to call it, what it returns, how to progress through it, and what happens with no project_id. No meaningful gap remains.

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?

The single parameter is fully documented in the schema and points to dosai_list_projects, so baseline is 3. The description adds genuine meaning beyond the schema by explaining the omitted-parameter behavior — the tool lists projects and explains how to start — which the schema does not state.

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 — returns the setup interview script — and anchors it to concrete owner phrasings ("настрой бота", "set everything up"). The enumeration of the 15 stages makes clear exactly what the tool produces, so an agent can distinguish it from a generic checklist or status tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger ("CALL THIS FIRST when the owner asks to set up, configure, finish or improve the bot"), explicit workflow ("Follow `rules`, go stage by stage, call it again after every few stages"), and an explicit no-argument path ("Without project_id: lists the projects and says how to start"). When-to-use and how-to-use are both spelled out.

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