Skip to main content
Glama

Uninstall Webhound MCP

webhound_uninstall
Read-onlyIdempotent

Removes Webhound MCP configuration and local rules from an agent workspace, reverting to default settings without revoking API keys.

Instructions

No-spend guidance for removing Webhound MCP config and Webhound-specific local rules from an agent workspace. Does not revoke keys automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientNogeneric
include_rules_cleanupNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
bodyNo
codeNo
dataNo
toolYes
errorNo
stepsNo
clientNo
statusNo
blockedNo
messageNo
summaryYes
no_spendNo
requiredNo
retryableNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
revokes_keyNo
client_labelNo
next_actionsNo
error_detailsNo
guidance_onlyNo
original_toolNo
action_startedNo
schema_versionYes
current_balanceNo
session_startedNo
key_revocation_noteNo
auto_recharge_enabledNo
likely_rule_locationsNo
user_message_templateNo
retry_after_user_confirmsNo
suggested_user_facing_wordingNo
Behavior1/5

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

The description claims the tool removes config and rules (modifying state), but annotations set 'readOnlyHint=true', indicating a read-only operation. This is a clear contradiction, reducing transparency and potentially misleading the agent.

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 concise (two sentences) and straight to the point. It could be slightly more structured but avoids unnecessary fluff.

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 the tool has two parameters, no required fields, and an output schema (not shown), the description is insufficiently complete. It omits parameter explanations and fails to fully cover the tool's behavior beyond the initial removal statement.

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

Parameters1/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 'removing config and local rules' but fails to describe the 'client' enum or the 'include_rules_cleanup' boolean, leaving the agent without crucial usage context.

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 uninstalls Webhound MCP config and local rules, using a specific verb ('uninstall') and resource. It distinguishes from siblings like 'webhound_stop' and 'webhound_resume', which have different purposes.

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?

The description lacks guidance on when to use this tool versus alternatives (e.g., 'webhound_stop' or 'webhound_resume'). It does not mention prerequisites, when not to use it, or suggest other tools for different scenarios.

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