Skip to main content
Glama

QueryMind

Check onboarding

onboarding_status
Read-onlyIdempotent

Return onboarding stage, status and next steps, with question examples when available.

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

Input Schema

NameRequiredDescriptionDefault
job_idNoOmit for the most recent onboarding job for the current database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 closed-world scope, so the safety profile is fully covered there. The description adds one real behavioral detail beyond that: 'question examples' are returned conditionally ('when available'), telling the agent the payload varies. It does not describe pagination, error behavior, or what an incomplete onboarding looks like.

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?

A single front-loaded sentence listing exactly the three returned fields plus the conditional extra, with no filler or redundant restatement of the title.

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 a full annotation set and a fully documented single optional parameter, the remaining burden is describing the return value, which the description does (stage, status, next steps, optional question examples). The only gap is the absence of any alternative-routing guidance among the many onboarding-related siblings.

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 description coverage is 100%, and the single optional 'job_id' already documents that omitting it targets the most recent onboarding job for the current database. The description adds nothing about the parameter, which is acceptable at full coverage but is a missed opportunity to note the most-recent-default behavior up front.

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 uses a clear verb+resource pattern ('Return onboarding stage, status and next steps') and even notes an optional payload ('question examples when available'). It stops short of distinguishing itself from the likely sibling 'onboard' or 'ask', so an agent must infer the boundary from names alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance; the description never routes the agent between this, 'onboard', 'ask', or 'clarify'. The only usable cue is the implicit notion of 'checking status', which is weak given the overlapping sibling set.

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