Skip to main content
Glama

Webhound Account

webhound_account
Read-onlyIdempotent

Check account credits, recent usage, and defaults without spending any budget.

Instructions

Read credits, recent usage, free-run status, and defaults. Does not spend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
bodyNo
codeNo
dataNo
toolYes
errorNo
usageNo
statusNo
billingNo
blockedNo
creditsNo
messageNo
summaryYes
defaultsNo
free_runNo
no_spendNo
requiredNo
retryableNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
next_actionsNo
authenticatedNo
error_detailsNo
original_toolNo
action_startedNo
schema_versionYes
current_balanceNo
session_startedNo
research_harnessNo
credit_balance_usdNo
auto_recharge_enabledNo
can_start_default_runNo
user_message_templateNo
retry_after_user_confirmsNo
can_start_default_paid_runNo
reserved_credit_balance_usdNo
available_credit_balance_usdNo
can_start_any_onboarding_runNo
credit_availability_verifiedNo
minimum_supported_budget_usdNo
can_start_any_onboarding_paid_runNo
can_start_standard_onboarding_runNo
can_start_standard_onboarding_paid_runNo
billing_configured_for_uninterrupted_runsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context by listing what information is read (credits, recent usage, etc.) and reinforcing safety. No contradictions exist between description and 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 two sentences long, front-loaded with the action and resources, and every word earns its place. No unnecessary information.

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

Completeness4/5

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

Given the tool has zero parameters, comprehensive annotations, and an output schema, the description is mostly complete. It could be slightly vague about 'recent usage' (time period not defined), but overall it sufficiently describes the tool's purpose.

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

Parameters4/5

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

There are no parameters, and schema description coverage is 100% trivially. The description does not need to add parameter info, and it correctly implies no input is needed. Baseline of 4 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 uses the specific verb 'Read' and lists the exact resources (credits, recent usage, free-run status, defaults). It clearly distinguishes from sibling tools by stating 'Does not spend', making it clear that this is a read-only account overview tool.

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 read-only usage by stating 'Does not spend', but it does not explicitly mention when to use this tool versus siblings like webhound_get_defaults or webhound_get_claims. No alternatives or exclusions are provided, leaving the agent to infer context.

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