Skip to main content
Glama

List webhook subscriptions

webhooks_list
Read-only

List webhook subscriptions (GET https://app.deepvalues.ai/api/v1/webhooks — no charge; needs a connected account or a dv_sk_ key)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webhooks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds non-obvious traits: it is free of charge, it requires either a connected account or a dv_sk_ key, and it hits a specific documented endpoint. Those are exactly the operational facts an agent needs before calling, and none are in the 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?

One sentence with the resource first and the operational facts packed into a single parenthetical, so there is zero filler. Every clause (endpoint, cost, auth) carries distinct 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?

For a zero-parameter read tool with no output schema, the definition covers cost, auth, and endpoint, which is most of what an agent needs. It stops short of describing the shape of a returned subscription (id, url, events, active status) or any pagination behavior, leaving the agent guessing at the response.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameters or filtering options.

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

Purpose4/5

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

States a specific verb and resource ('List webhook subscriptions'), so there is no ambiguity about what the tool returns. The title repeats the same phrasing, and there is no sibling webhook tool to distinguish from, so the differentiation burden is minimal but unexploited.

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 parenthetical gives prerequisites (connected account or dv_sk_ key) and cost ('no charge'), which tells the agent whether it can call it, but not when to prefer this over another approach. There are no stated exclusions or alternatives, so usage is only implied by the name.

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.

Resources