Skip to main content
Glama

Add Webhound Budget

webhound_add_budget

Allocate a research budget to a session, setting effort level for investigation, with optional context, guidance, and file references.

Instructions

Add research budget and optional guidance/context to a session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
file_idsNo
guidanceNo
session_idYes
context_session_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
agentsNo
alertsNo
amountNo
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
agent_instructionNo
completion_reasonNo
followup_check_inNo
assembly_triggeredNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
retry_after_user_confirmsNo
Behavior2/5

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

Annotations indicate the tool is not read-only, not idempotent, and not destructive, but the description adds minimal behavioral context. It does not disclose whether multiple calls accumulate budget or override, nor does it mention any prerequisites or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence and front-loads the main action, but it sacrifices clarity for brevity. It could be longer to cover missing parameter semantics while remaining concise.

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

Completeness2/5

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

Given 5 parameters, 0% schema coverage, and a similar sibling tool, the description is insufficient. It fails to explain the meaning of 'add' vs 'set', the role of 'file_ids', or the expected format of 'guidance'. The output schema exists but does not compensate for input ambiguity.

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 coverage is 0%, so the description must explain parameters. It mentions 'amount', 'guidance', and 'context' (implied by 'context'), but omits 'session_id' and 'file_ids'. No details on format, constraints, or relationships between parameters are given.

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 tool adds a research budget and optional guidance/context to a session. However, it does not differentiate from the sibling 'webhound_set_budget', which could lead to confusion about whether 'add' means increment or initial set.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not specify when to use this tool over alternatives like 'webhound_set_budget' or other session-modifying tools, leaving the agent without context for selection.

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