Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

contacts_sync

Add a discovered contact and open a conversation thread. Returns thread_id for the new conversation, plus entity_id — the canonical handle to pass as contacts.update's contact_id. Call contacts.discover first to verify the contact exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel name: telegram, whatsapp, etc.
identifierYesUsername or phone number to add
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
from_account_idNoWhich of the workspace's accounts on this channel opens the conversation — i.e. WHO the contact will see as the sender. OMIT and the platform picks the account that already holds most of this workspace's threads. Pass it whenever the sender matters: a workspace with several numbers on one channel usually has one that must not start conversations (a personal line, or one under a spam restriction). An account that is not active in this workspace is refused, never silently swapped for another.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a mutating, non-idempotent, open-world operation, so the safety profile is covered. The description adds real value beyond that: it discloses the return values (thread_id, entity_id), the downstream linkage (entity_id is the handle for contacts_update's contact_id), and a precondition. It does not warn that repeat calls create duplicate threads, but that is a modest gap given the annotation coverage.

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 tight sentences: action first, return values second, prerequisite third. Every sentence carries distinct information and nothing is redundant with the schema or annotations.

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?

With no output schema, the description carries the burden of explaining returns and does so adequately (thread_id, entity_id plus its downstream use). Prerequisites and the mutation profile are covered by annotations, but the description is silent on whether opening a conversation actually sends a visible message to the contact — relevant given openWorldHint=true.

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?

Schema description coverage is 100%, so channel, identifier, in_workspace, and from_account_id are already fully documented in the schema, including the detailed from_account_id sender-selection guidance. The description adds no parameter-level detail beyond the return-value linkage, so the baseline 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?

States a specific verb and resource: 'Add a discovered contact and open a conversation thread.' The phrase 'discovered contact' plus the reference to contacts.discover implies this registers a pre-existing contact rather than creating one from scratch, partially distinguishing it from siblings like contacts_add_channel or contacts_capture_lead, though it never names those alternatives directly.

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?

Gives a clear ordered prerequisite: 'Call contacts.discover first to verify the contact exists.' That tells the agent when this tool is appropriate in the workflow. It stops short of stating when NOT to use it or naming which sibling to prefer for other contact operations.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources