Skip to main content
Glama

households_webhooks_get_all

Retrieve all webhooks for households with options for sorting, filtering, and pagination.

Instructions

Get All [GET /api/households/webhooks]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
orderByNo
perPageNo
queryFilterNo
orderDirectionNodesc
paginationSeedNo
orderByNullPositionNo
Behavior2/5

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

No annotations provided, and the description does not disclose that the tool is read-only, what data is returned, or any side effects. Minimal transparency for a potentially paginated endpoint.

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

Conciseness2/5

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

Excessively concise with only two words, failing to include essential context that could fit in the same space.

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

Completeness1/5

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

No output schema, no annotations, and a minimal description. The tool is severely under-documented given its 7 parameters and lack of behavioral cues.

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?

The description offers no explanation for any of the 7 parameters, despite 0% schema coverage. It does not add meaning beyond the schema structure, leaving agents to guess parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get All' combined with the path suggests it retrieves all webhooks for the household, but it is extremely terse and does not explicitly state the resource or scope, leaving room for ambiguity among similar sibling tools.

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 guidance on when to use this tool versus siblings like households_webhooks_get_one or other get_all tools. Lacks context about pagination or filtering options.

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/2fst4u/mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server