Skip to main content
Glama
Sign In
SlingHook

SlingHook

by DylanCourtney584
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List events

list_events
Read-only

List webhook events captured on an endpoint as short summaries, newest first, and filter by method, signature status, or search query.

Instructions

Lists webhooks captured on an endpoint, newest first, as short summaries (number, time, method, event type, signature status) without bodies. Use get_event for one event in full. Without query or before_id it reads the newest events (up to 50, every plan). query and before_id search the whole retained history, which needs the Pro plan.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many events to return
queryNoPro: free text to find in bodies, headers and notes, or a JSON path match such as `type = invoice.paid` or `data.object.id = in_123` (`!=` to exclude)
methodNoOnly this HTTP method, e.g. POST
endpointYesEndpoint UUID, catch URL (https://…/c/<id>) or reserved slug, as list_endpoints shows it
before_idNoPro: page further back; pass next_before_id from the previous result
signatureNoOnly events whose signature check had this result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish a safe read (readOnlyHint, openWorldHint=false), but the description adds real substance: summaries are body-less, results are ordered newest-first, the non-paged read caps at 50 on every plan, and whole-history search requires Pro. It does not mention pagination cursor semantics beyond before_id or result envelope details, but coverage is strong for a list tool.

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?

Three tightly packed sentences: what it returns, where to go for the full event, then the two modes and their plan constraints. No filler and the core behavior leads.

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

Completeness5/5

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

With no output schema, the description correctly spends its words on the returned summary fields and the body exclusion, which an agent needs to know. Plan limits, ordering, and the alternate tool are all covered, leaving no material gap for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining the coupling between the absence/presence of query and before_id and which data set (newest vs. retained history) is scanned. It repeats the Pro gating already present in the schema descriptions, so it stops short of a 5.

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?

States a specific verb and resource ('Lists webhooks captured on an endpoint') plus scope ('newest first') and the exact shape of what comes back (number, time, method, event type, signature status, no bodies). It also distinguishes itself from get_event, so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to get_event for a full single event, and explains that omitting query/before_id gives the newest events while supplying them searches retained history. It even names the plan gating each mode, which is the main decision factor for an agent choosing a call strategy.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools