Skip to main content
Glama

What's left to set up

onboarding_status
Read-only

Checklist of what this workspace still needs before every feature works (Herman, compliance agreement, phone number, crew, your mobile, credits, Salesforce, Google, texting, team), in the order to do them, with the tool or link for each. Start here after signing up.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to re-establish safety. It does add useful behavioral detail beyond them: the response is ordered by execution sequence and each entry carries the tool or link that resolves it, which is meaningful for a tool with no output schema. Rate limits or behavior for a partially configured workspace are not covered.

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?

Purpose is front-loaded in the first clause, and the trailing 'Start here after signing up' lands the routing advice. The long parenthetical enumerating checklist categories adds real information about scope but is bulky and slightly noisy ('Herman', 'your mobile' alongside 'phone number' are not obviously distinct).

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?

For a zero-parameter, no-output-schema read tool this is close to sufficient: it conveys what comes back (ordered checklist with resolving tool/link per item) and where it fits in the flow. It could say more about what a fully-configured workspace returns, but nothing essential to invocation is missing.

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 baseline of 4 applies and there is no parameter ambiguity to resolve. The description correctly spends its words on the return content instead of inventing inputs.

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 concrete verb+resource: a checklist of what the workspace still needs before every feature works. The enumerated items (compliance agreement, phone number, crew, credits, Salesforce, Google, texting) make it unmistakable against siblings like credits_status or whoami, which report a single state rather than the full setup path.

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?

'Start here after signing up' gives clear entry-point guidance for new workspaces and implies this is the first call before the individual setup tools. It stops short of saying when not to call it (e.g. once setup is complete, or when only one specific gap needs checking via credits_status/whoami), so no explicit exclusion is offered.

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.