list_templates
Ingest snippets and the JSON HookPulse POSTs on a miss.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
hookpulse
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1.6/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It gives a cryptic phrase about ingesting snippets and POSTing on a miss, which does not explain what the tool actually does, what side effects occur, or what happens when invoked.
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?
The description is short but not informative; it is under-specified rather than concise. The words do not earn their place because they obscure rather than clarify the tool's purpose.
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?
For a zero-parameter listing tool, a complete description could be as simple as 'List all templates.' The provided text fails to identify the resource or operation, making the tool effectively uncallable for an agent trying to understand what it does.
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?
The tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description adds no parameter meaning, but none is needed for an empty input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Ingest snippets and the JSON HookPulse POSTs on a miss' does not state that this tool lists templates; it describes an ingestion/fallback behavior that conflicts with the tool name. It lacks a clear verb+resource mapping and does not differentiate from sibling list tools like list_endpoints or list_events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool versus alternatives. The description does not mention templates, listing, or any condition that would lead an agent to select this tool over its siblings.
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
C2.8/5.0
Disambiguation5/5
Each tool targets a distinct resource or action: endpoint lifecycle, guest tokens, events, templates, billing, contact, health, and status feeds are clearly separated. Even related tools like get_endpoint and list_endpoints have clearly different scopes.
Naming Consistency3/5
The create_/get_/list_/delete_ prefix pattern is consistent for resource operations, but several tools are bare nouns (api_index, billing, contact, health, status_feed_url) and status_feed_rotate reverses the expected verb-object order. The mixed style reduces predictability.
Tool Count5/5
Fourteen tools is within the ideal scope for an API-focused server, and each tool provides a meaningful capability for using the HookPulse service. The count feels complete without being bloated.
Completeness4/5
The endpoint lifecycle is well covered with create, get, list, and delete, plus supporting features like events, templates, status feeds, and billing. There is no explicit update/pause endpoint operation, but that may be outside the dead-man endpoint model, so the gap is minor.