Skip to main content
Glama

Outgoing webhooks of the project

dosai_list_integrations
Read-onlyIdempotent

The owner's own integrations: addresses that receive the project's events (new lead, new message and so on), which events each gets and whether it is on. CRM: dosai_get_crm_integration. Altegio, YCLIENTS, iiko: dosai_get_booking_system.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds value beyond that by describing the shape of what comes back (destinations, per-integration event subscriptions, on/off state), which is the main missing piece since there is no output schema. It does not mention pagination or whether disabled webhooks are included.

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?

Two compact sentences: the first defines the tool's scope and payload, the second dispatches to the two sibling tools. Every clause carries information and the routing guidance is placed after the primary scope, so it reads front-loaded.

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 single-parameter read listed against a rich sibling set, the definition covers purpose, return contents and alternatives, which is largely sufficient given the annotations carry the safety profile. The only soft spot is the 'owner's own integrations' framing, which could be read as account-level rather than project-level and is not reconciled with project_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required project_id whose schema description already points to dosai_list_projects, giving 100% schema description coverage. The description adds no further meaning about that parameter, so the schema does the work and the baseline of 3 applies.

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?

The description identifies the resource precisely as the project's outgoing webhook integrations and even enumerates what each entry carries (receiver address, subscribed events, enabled flag). The verb is implicit rather than stated, and the phrase 'The owner's own integrations' is slightly at odds with the project_id parameter, but an agent can tell this apart from the CRM and booking-system siblings 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?

It explicitly routes the agent away to alternatives with the condition that selects them: CRM integrations go to dosai_get_crm_integration, and Altegio/YCLIENTS/iiko go to dosai_get_booking_system. That leaves this tool clearly scoped to generic outgoing webhooks, with nothing left to infer.

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