Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List webhooks

list_webhooks
Read-only

Retrieve the webhook endpoints configured in a Cmssy workspace to review integrations. Signing secrets are never included in the response.

Instructions

List the workspace's webhook endpoints (signing secrets are never returned here).

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": "list_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: results are scoped to the current workspace, and signing secrets are deliberately excluded from the response — a security-relevant detail an agent cannot get from 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?

A single sentence with the resource named first and the most surprising constraint (secrets are never returned) placed in immediate parenthesis. Nothing is wasted and nothing important is buried.

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-argument, read-only list with no output schema and full annotation coverage, the description covers purpose, scope, and one critical caveat. The remaining omission — result shape, ordering, or pagination behavior — is minor but would help an agent reason about response handling.

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 zero parameters, so per the baseline this sits at 4. The description correctly adds no parameter narrative, though it also does not mention whether results are paginated or default-ordered.

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?

"List the workspace's webhook endpoints" gives a specific verb and resource, and the word "endpoints" implicitly separates this from sibling list_webhook_deliveries and list_webhook_event_types. It stops short of explicitly naming those siblings, so the differentiation is inferential rather than stated.

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?

Usage is only implied: an agent can infer this is the browsing tool for webhook configuration, but there is no explicit when-to-use, no mention of list_webhook_deliveries for delivery history, and no prerequisites or exclusions. For a zero-parameter list call that is a tolerable but real gap.

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