Skip to main content
Glama

What is still missing

dosai_get_setup_checklist
Read-onlyIdempotent

Is the bot ready for real clients: description, channel, balance, a test conversation, and the optional extras. The same short checklist the owner sees on the project overview. To lead the owner through the whole setup (functions, tags, follow-ups, reports, integrations) use dosai_get_setup_guide instead.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_get_setup_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom 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.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description adds scope instead: it is a short readiness checklist mirroring the project overview UI, not a configuration or mutation tool. It does not say what a failing or incomplete item looks like, so it stops short of full disclosure, but with annotations carrying safety this is solid.

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. The scope enumeration comes first, then the routing exclusion — exactly the order an agent needs to decide and act.

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 carries the burden of explaining what comes back, and it does so by enumerating the checklist dimensions plus the mention of 'optional extras'. It does not indicate the result shape (per-item status, pass/fail, counts), which is the remaining gap, but an agent can tell whether this tool answers its question.

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?

There is a single parameter and the schema already documents it fully ('From dosai_list_projects.', uuid format, required). The description adds no additional meaning about the project_id, so the baseline 3 applies — the schema does all the work here.

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 concrete resource (a readiness checklist) and enumerates exactly what it covers: description, channel, balance, a test conversation, and optional extras. It explicitly distinguishes itself from dosai_get_setup_guide, which is the strongest form of sibling differentiation. It loses a point only because the action is phrased as a rhetorical question ('Is the bot ready...') rather than a stated verb like 'returns a readiness checklist'.

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?

It names the alternative (dosai_get_setup_guide) and the exact condition that selects it ('to lead the owner through the whole setup'). That routing rule is unambiguous and is reinforced by 'the same short checklist the owner sees on the project overview', which tells the agent when this view is appropriate.

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