Skip to main content
Glama

Webhound Onboarding

webhound_onboarding
Read-onlyIdempotent

Guides new users through onboarding with client-aware flows: setup-first for local agents, research-first for hosted clients. Budget determines research depth, with time allocation based on tier.

Instructions

No-spend, client-aware guided onboarding. Local agents receive the full setup-first versus jump-in flow; hosted clients receive a research-first flow with no filesystem setup unless the user explicitly requests approval-gated workspace-rule guidance. Budget maps to about 15 minutes per $1: $5 is about 75 minutes and $20 is about 300 minutes (5 hours). The $2/$5/$10/$20 tiers are starting points, not caps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientNoIdentify the calling agent when known. Omitted or generic callers receive the research-first, filesystem-safe flow.generic
capabilitiesNo
workspace_rules_requestedNoSet true only when the user explicitly asks for workspace-rule guidance as a separate action.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
bodyNo
codeNo
dataNo
stepNo
toolYes
errorNo
clientNo
statusNo
billingNo
blockedNo
choicesNo
flow_idNo
messageNo
summaryYes
free_runNo
no_spendNo
requiredNo
retryableNo
setup_flowNo
top_up_urlNo
api_messageNo
billing_urlNo
client_modeNo
next_actionNo
budget_modelNo
flow_versionNo
next_actionsNo
account_stateNo
error_detailsNo
flow_sequenceNo
hosted_safetyNo
original_toolNo
action_startedNo
agent_playbookNo
budget_summaryNo
schema_versionYes
current_balanceNo
session_startedNo
workspace_rulesNo
onboarding_versionNo
recommended_defaultsNo
setup_timing_choicesNo
user_facing_guidanceNo
auto_recharge_enabledNo
suggested_agent_rulesNo
topic_change_behaviorNo
user_message_templateNo
first_artifact_choicesNo
immediate_next_messageNo
retry_after_user_confirmsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context: it's 'No-spend', guided, and client-aware with specific flow differences. It aligns with annotations and adds value beyond them.

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 concise with 4 sentences, front-loaded with the core purpose, and each sentence adds meaningful information without redundancy.

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?

Given the tool's complexity (nested objects, output schema), the description covers the main behavioral aspects—client-aware flows and budget mapping. The output schema handles return values, so no further detail is needed. Minor gap: does not explain the capabilities parameter's role.

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?

Schema coverage is 67% with descriptions for client and workspace_rules_requested. The description adds meaning by explaining the flow differences for 'hosted' vs 'local' clients and how workspace_rules_requested is only honored when user explicitly asks. The capabilities parameter is not described, but the description partially compensates.

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 clearly states that the tool provides 'No-spend, client-aware guided onboarding' and distinguishes between local and hosted clients, specifying different flows. This uniquely identifies the tool's purpose among sibling tools like webhound_help or webhound_account.

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?

The description explains when to use the tool (onboarding new agents) and provides context for different client types (local vs hosted) and budget mapping. It does not explicitly mention when not to use or provide direct alternatives, but the context is clear enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WebhoundAI/webhound-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server