Skip to main content
Glama

Get Webhound Evidence Pack

webhound_get_evidence_pack
Read-onlyIdempotent

Retrieve the full evidence pack from a completed Webhound session, including working documents, claim traces, sources, and export links, to inform follow-up research.

Instructions

Read the full evidence payload for a completed Webhound session: final output, working docs, claim traces, sources, and export links. Use this before serious follow-up answers so Webhound value is not reduced to only the polished output document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoauto
session_idYes
allow_partialNoSet true only if the user explicitly asks for an interim evidence snapshot before done=true.
include_claimsNo
include_sourcesNo
include_working_docsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
tasksNo
usageNo
agentsNo
alertsNo
budgetNo
claimsNo
outputNo
statusNo
blockedNo
datasetNo
exportsNo
healthyNo
messageNo
notepadNo
omittedNo
productNo
resumedNo
sessionNo
sourcesNo
stoppedNo
summaryYes
acceptedNo
activityNo
artifactNo
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
actual_kindNo
api_messageNo
billing_urlNo
diagnosticsNo
next_actionNo
total_spentNo
amount_addedNo
content_hashNo
credit_limitNo
generated_atNo
next_actionsNo
output_readyNo
session_typeNo
working_docsNo
current_spendNo
error_detailsNo
original_toolNo
sidecar_notesNo
action_startedNo
budget_controlNo
current_budgetNo
guidance_addedNo
requested_kindNo
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
excluded_by_requestNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
complete_evidence_packNo
evidence_pack_instructionNo
next_research_instructionNo
retry_after_user_confirmsNo
evidence_pack_deferred_until_doneNo
Behavior3/5

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

Annotations already declare the tool as read-only and idempotent. The description adds context about the content of the evidence pack but does not disclose additional behavioral traits like authorization needs, rate limits, or behavior for incomplete sessions. It does not contradict annotations.

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 only two sentences, both purposeful. The first sentence defines the action and deliverables, the second provides usage advice. No redundant or extraneous information.

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

Completeness3/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, the description need not detail return values. However, with 6 parameters and low schema coverage, the description lacks parameter guidance, and it does not specify prerequisites (e.g., session must be completed). It is adequate but not fully comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (17% - only allow_partial has a description). The tool description does not explain any parameters or their defaults, leaving the agent to rely on parameter names which are reasonably self-explanatory but lack formal guidance.

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 tool reads the full evidence payload for a completed Webhound session, listing specific components (final output, working docs, claim traces, sources, export links). This distinguishes it from siblings like webhound_get_output and webhound_get_claims.

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 explicitly advises using this tool before serious follow-up answers to preserve Webhound value, implying a when-to-use scenario. It does not explicitly mention when not to use it or list alternatives, but the guidance is clear and contextual.

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