Skip to main content
Glama

Update Webhound Sidecar Note

webhound_update_sidecar_note
Destructive

Edit, restore, or dismiss a shared research note for a Webhound session without spending budget or interrupting the investigation cycle.

Instructions

Edit, restore, or dismiss one shared sidecar note. No spend. Does not interrupt the Planner/Executor/Verifier cycle and does not change session status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoSet to dismissed to remove it from future planner intake; set to pending to restore it.
note_idYes
summaryNoConcise sourced note or hypothesis for Webhound to consider later.
confidenceNo
hypothesisNoSet true only when this is explicitly a hypothesis without source URLs.
session_idYes
source_urlsNoSource URLs backing the note. Required unless hypothesis=true.
why_it_mattersNo
suggested_angleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
bodyNo
codeNo
dataNo
noteNo
toolYes
errorNo
statusNo
blockedNo
messageNo
summaryYes
updatedNo
no_spendNo
requiredNo
retryableNo
session_idNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
interruptingNo
next_actionsNo
error_detailsNo
original_toolNo
action_startedNo
schema_versionYes
current_balanceNo
session_startedNo
auto_recharge_enabledNo
user_message_templateNo
retry_after_user_confirmsNo
Behavior4/5

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

Beyond annotations (destructiveHint, openWorldHint), the description adds 'No spend' and non-interruption guarantees, which are key behavioral traits. It does not elaborate on side effects of dismissal or restoration.

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 extremely concise: one sentence stating purpose, followed by two short behavioral statements. Every word adds value, and key information is front-loaded.

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 9 parameters and a destructive hint, the description is brief. It does not explain return values from the output schema, nor does it detail what 'dismiss' entails beyond what the schema says. Some gaps remain, but the core purpose is clear.

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 description coverage is 44%, and the tool description does not add any parameter-level information. The actions (edit, restore, dismiss) imply which parameters are relevant but do not clarify their semantics beyond the schema.

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 'Edit, restore, or dismiss one shared sidecar note,' which are specific actions on a well-defined resource. It distinguishes from siblings like add_sidecar_notes and list_sidecar_notes by focusing on modification.

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 provides context on when to use: 'No spend. Does not interrupt the Planner/Executor/Verifier cycle and does not change session status.' This implies it's safe for routine modifications. However, it does not explicitly mention when to use alternatives like add_sidecar_notes.

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