Skip to main content
Glama

Resume Webhound Session

webhound_resume

Resume a paused or completed research session with optional additional budget and guidance to continue the investigation.

Instructions

Resume a paused/completed/awaiting-input session with optional additional budget and guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idsNo
guidanceNo
session_idYes
additional_budgetNo
context_session_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
agentsNo
alertsNo
budgetNo
statusNo
blockedNo
datasetNo
healthyNo
messageNo
productNo
resumedNo
stoppedNo
summaryYes
acceptedNo
activityNo
free_runNo
no_spendNo
requiredNo
documentsNo
retryableNo
checked_atNo
is_runningNo
message_idNo
new_budgetNo
session_idNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
total_spentNo
amount_addedNo
credit_limitNo
next_actionsNo
output_readyNo
session_typeNo
current_spendNo
error_detailsNo
original_toolNo
action_startedNo
budget_controlNo
current_budgetNo
guidance_addedNo
schema_versionYes
current_balanceNo
mcp_next_actionNo
previous_budgetNo
session_startedNo
status_snapshotNo
completion_stateNo
research_harnessNo
runtime_estimateNo
sidecar_guidanceNo
additional_budgetNo
agent_instructionNo
completion_reasonNo
followup_check_inNo
assembly_triggeredNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
retry_after_user_confirmsNo
Behavior4/5

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

The description adds context beyond annotations by specifying the allowable session states for resumption and optional parameters. Annotations already indicate the tool is not read-only or destructive, and the description clarifies the mutation is a resume operation. No contradictions.

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 a single sentence that efficiently conveys the tool's core purpose and optional features without extraneous words.

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 presence of an output schema and annotations, the description adequately covers when to use the tool and its basic behavior. It could mention error handling (e.g., if session not found) but is largely complete for the complexity level.

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?

With 0% schema coverage, the description partially compensates by explaining 'additional budget' and 'guidance' parameters. However, it omits 'file_ids' and 'context_session_ids', leaving their purpose unclear. schema coverage is high.

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 clearly states the verb 'Resume' and the resource 'Webhound Session', specifying the session states that can be resumed (paused/completed/awaiting-input). However, it does not explicitly distinguish this tool from siblings like 'webhound_start_report' or 'webhound_wait'.

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

Usage Guidelines3/5

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

The description mentions optional additional budget and guidance, hinting at when to use these parameters. However, it provides no guidance on when not to use this tool (e.g., if session is still active) or alternatives like 'webhound_wait' for running sessions.

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