Skip to main content
Glama

Keelen

by io.github.jamie7893

get_onboarding_status

Read-onlyIdempotent

Check what is set up so far and what to do next to get building.

Reports engine_connected / github_connected / project_count / payment_status
and a `next_action` string you should follow VERBATIM, polling this tool
between steps. `next_action` is "call_tool" (call the tool named in
`next_tool`, following `next_step`) until onboarding is complete, then
"done". (`next_action_detail` echoes the pre-2026-07-29 dict shape and is
DEPRECATED — it is removed 2026-10-29; read next_action/next_tool instead.)
- engine step: send the user the dashboard /login link. Engine subscriptions
  (Claude / Codex / GLM) are connected in the DASHBOARD for security —
  NEVER ask for or paste engine credentials in this chat.
- github step: call connect_github() for an install link.
- project step: create_project(...) for a new repo, or
  import_project(repo_full_name) for an existing one.
- launch step: poll get_provisioning_status(project_id) until ready.
Re-checking is YOUR job — the server does not push.
Also returns a `usage` block (pool / daily / machine-hours counters + tier
caps) for capacity-aware automation clients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond these: the need to poll repeatedly, the meaning of `next_action` and `next_action_detail` deprecation, a security warning about credentials, and the `usage` block for capacity awareness. No contradictions with annotations.

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?

The description is front-loaded with a one-line summary, then uses bullet-like lines for steps. Every sentence earns its place: security instructions, deprecation notice, polling behavior, and usage block. It is appropriately detailed for the complexity of the onboarding flow without unnecessary fluff.

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?

Despite no parameters, the tool has a complex output schema and workflow. The description fully covers return fields, the `next_action` state machine, step-specific actions, deprecation, security, and the usage counters. It is complete enough for an agent to use the tool correctly without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema provides no parameter semantics. The description compensates richly by explaining the output structure and how to interpret `next_action`, `next_tool`, and the deprecated field, far exceeding the baseline for a zero-parameter tool.

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?

The description opens with a clear, specific statement: 'Check what is set up so far and what to do next to get building.' It names the exact resources (engine_connected, github_connected, project_count, payment_status) and the `next_action` flow, distinguishing it clearly from sibling tools like get_provisioning_status or project_status.

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?

Provides explicit step-by-step usage: engine step (send dashboard /login link, never ask for credentials), github step (call connect_github), project step (create_project or import_project), launch step (poll get_provisioning_status). It also states polling is the agent's responsibility ('Re-checking is YOUR job'), giving clear when-to-use and alternative-tool guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Keelen toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action duo, even within clusters like request handling or security reviews. The get_ vs run_ pairs are clearly separated, and descriptions explicitly contrast confusing alternatives such as archive_project vs delete_project.

Naming Consistency4/5

The set overwhelmingly follows verb_noun snake_case (submit_request, list_projects, resolve_escalation). The one visible deviation is project_status, which breaks the get_/pattern, and signup is a single-word verb instead of sign_up.

Tool Count2/5

37 tools is well above the 25+ threshold and spans auth, billing, project lifecycle, roadmap, escalations, product documents, and multiple review types. Most tools earn their place, but the surface is too large for one server and would be more coherent split into focused servers.

Completeness4/5

The domain coverage is broad: full project lifecycle, request intake/refinement, roadmap manipulation, escalation handling, product doc read/write, and security/legal review flows. Minor gaps exist, most notably no dedicated task-listing or task-update tool, but agents can work around these via project_status and list_escalations.

Resources