subfeed_webhook
Send a webhook payload to a public entity. No auth required.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Public entity ID | |
| payload | Yes | JSON payload to send |
Subfeed
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must convey all behavioral traits. It mentions 'No auth required' and that it sends a webhook payload, but fails to disclose outcomes, side effects, reversibility, or any error/response behavior. This is a side-effecting operation with minimal transparency.
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 exceptionally concise, two short sentences with zero filler. It front-loads the core action and adds the auth trait, making efficient use of words.
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 no output schema, the description should explain what happens after sending, but it does not. It also fails to differentiate from sibling tools or note any constraints, leaving the agent under-informed for a side-effecting webhook call.
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 coverage is 100%, with id described as 'Public entity ID' and payload as 'JSON payload to send'. The description adds no new information beyond the schema, so it meets the baseline for high coverage but does not enhance understanding.
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 a specific verb ('Send') and resource ('webhook payload to a public entity'), clearly distinguishing it from sibling tools like subfeed_chat or subfeed_create_entity. It is direct and unambiguous about the tool's primary function.
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 provides no guidance on when to use this tool versus alternatives like subfeed_invoke or subfeed_publish_entity. It states only the action itself without any contextual cues or exclusions, leaving selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a clear, distinct operation: entity CRUD, addon management, discovery, interaction, and registration. While chat, invoke, and webhook all involve communication, their descriptions clearly differentiate entity chat from public invocation and webhook payloads.
Naming Consistency4/5
All tools share the 'subfeed_' prefix and use snake_case, with most following a verb_noun pattern (create_entity, delete_entity, list_addons). A few use bare verbs (chat, invoke, register) or noun-only (webhook), but the pattern is still recognizable and predictable.
Tool Count5/5
15 tools is at the upper edge of the ideal range, but it matches the server's broad scope covering entities, addons, models, discovery, and user registration. Each tool serves a distinct purpose and none feel redundant.
Completeness4/5
The surface covers full entity lifecycle (create, get, update, delete, publish), addon management (enable, disable, list), entity discovery, and user registration. Minor gaps like an explicit unpublish or webhook management can be worked around via update_entity or standalone webhook sending.