Thesma MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_webhook

Retrieve details for a webhook subscription using its subscription ID, such as status, configuration, and metadata. Useful for verifying and managing subscription settings.

Instructions

Get details for one webhook subscription by id (e.g. 'sub_abc123').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subscription_id": "<subscription_id>"
    },
    "name": "get_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`subscription_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It does clearly indicate a read operation ('Get details'), but it provides no information on error behavior, authentication needs, rate limits, or any other side effects. The example id format adds a small amount of context, but overall it's minimal.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and resource, and the parenthetical example is useful without bloating the text.

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 simple get-by-id operation with an output schema available, the description is largely complete. It identifies the resource and how to specify it. It could mention error cases or that it returns full subscription details, but given the simplicity, the current level is adequate.

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 schema has no description for subscription_id and 0% coverage, so the description must compensate. It does so by giving a concrete example id ('sub_abc123'), which clarifies the expected format. This is helpful, though it doesn't explain where to find the id or any constraints.

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 clearly states the action ('Get details'), the resource ('webhook subscription'), and the scope ('one ... by id'), with an example id format. This distinguishes it from list_webhooks (which lists all) and other 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 Guidelines4/5

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

The 'by id' phrasing clearly implies this tool is for retrieving a specific subscription when you already have its identifier. While it doesn't explicitly mention alternatives like list_webhooks, the context is clear enough for the intended use case.

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

Deploy Server