Skip to main content
Glama

Get Webhound Session

webhound_get_session
Read-onlyIdempotent

Retrieve the complete session data including prompts, messages, documents, claims, and history in a single uncapped response with no pagination or truncation.

Instructions

Read the complete canonical session in one uncapped response: prompts, messages, phases, tasks, agents, final and working documents, dataset rows, claims, sources, notes, diagnostics, usage history, and artifact links. Nothing is paginated, truncated, or omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
notesNo
tasksNo
usageNo
agentsNo
alertsNo
budgetNo
statusNo
blockedNo
datasetNo
healthyNo
messageNo
notepadNo
omittedNo
productNo
resumedNo
sessionNo
stoppedNo
summaryYes
acceptedNo
activityNo
evidenceNo
free_runNo
messagesNo
metadataNo
no_spendNo
requiredNo
artifactsNo
documentsNo
retryableNo
truncatedNo
checked_atNo
is_runningNo
message_idNo
new_budgetNo
session_idNo
top_up_urlNo
api_messageNo
billing_urlNo
diagnosticsNo
next_actionNo
total_spentNo
amount_addedNo
content_hashNo
credit_limitNo
generated_atNo
next_actionsNo
output_readyNo
session_typeNo
current_spendNo
error_detailsNo
original_toolNo
sidecar_notesNo
action_startedNo
artifact_linksNo
budget_controlNo
current_budgetNo
guidance_addedNo
research_stateNo
schema_versionYes
current_balanceNo
mcp_next_actionNo
phase_summariesNo
previous_budgetNo
research_agentsNo
session_startedNo
status_snapshotNo
complete_sessionNo
completion_stateNo
content_markdownNo
research_harnessNo
runtime_estimateNo
session_revisionNo
sidecar_guidanceNo
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?

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower. The description adds valuable context: 'uncapped response', 'nothing is paginated, truncated, or omitted', which discloses behavior beyond schema. No contradiction with annotations.

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?

The description is a single sentence that efficiently lists all components of the session. It is front-loaded with the core action and resource. Slightly dense with commas, but no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, simple-parameter tool with an output schema, the description covers all necessary context: what the tool does, what it returns, and key behavioral traits (no pagination). No gaps identified.

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 coverage is 0%, but the single parameter 'session_id' is self-explanatory. The description implies its purpose by mentioning session, but does not add explicit detail about the parameter's format or constraints. Baseline 3 is appropriate.

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 the verb 'Read' and the resource 'complete canonical session', listing all included data types. It distinguishes from siblings like webhound_get_output or webhound_get_claims by emphasizing the comprehensive, uncapped nature.

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 implies use when needing the full session, but does not explicitly state when not to use or mention alternatives. Sibling tools exist for partial data, but no comparative guidance is given.

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