Skip to main content
Glama

QueryMind

Start onboarding

onboard

Start a durable job to learn the connected database structure. Reuses a running job for the same database. Check onboarding_status; candidates requiring approval are handled with review.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The description adds real value beyond the annotations: it discloses that the work is a durable background job and that a running job for the same database is reused, which is behavior an agent cannot infer from readOnlyHint=false or idempotentHint=false. However, it does not say what the caller receives back (job handle, status object) or how failures/timeouts surface, leaving the async lifecycle partially opaque.

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?

Three short sentences with zero filler, ordered correctly: what happens, the reuse nuance, then the follow-up actions. The core verb and resource lead the text so an agent scanning the first clause gets the gist.

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 parameters and no output schema, the description carries the whole burden, and it covers initiation, reuse, polling, and approval routing. The remaining gap is what a call returns and what happens if the job fails, which matters for an agent deciding whether to block on the result.

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 tool takes zero parameters, so the description has no parameter semantics to compensate for and the baseline applies. The implicit scoping — 'the connected database' and 'same database' — usefully clarifies that no database argument is required.

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 pairs the specific verb 'Start' with a specific resource, 'a durable job to learn the connected database structure,' making the async/batch nature of the operation explicit up front. An agent can distinguish this from onboarding_status (polling) and review (approval) without opening any schema.

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?

It clearly routes the agent: poll with onboarding_status and handle approval-requiring candidates via review, which is concrete next-step guidance referencing siblings. It stops short of stating when not to call it (e.g. whether calling while onboarding is already complete is wasted) or any prerequisite such as a connected database.

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