Sergio by Serviche

Link a conversation to a contact

link_conversation_to_client

Idempotent

Links a conversation to a contact, as the inbox's Link to a contact does: if the contact already has a one-to-one thread, it is folded into this one, and an email thread's address is saved to the contact. Sergio learns the correction for later emails. Pass the same idempotency_key when retrying.

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": {
      "conversation_id": "<conversation_id>",
      "client_id": "<client_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "link_conversation_to_client"
  }
}

Input Schema

Name	Required	Description
`client_id`	Yes
`conversation_id`	Yes
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare it as a non-destructive, idempotent write. The description adds valuable side-effect context: folding an existing one-to-one thread, saving an email address to the contact, and learning the correction for later emails. Doesn't cover permissions or error behavior, but adds significant transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action. Every sentence contributes: first states the action and its effects, second gives a retry instruction. Minor redundancy with schema on idempotency_key, but overall efficient.

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 mutation tool with no output schema, the description covers key behavioral aspects (side effects, idempotency retry). Missing details like permissions or return value, but annotations already convey safety and idempotency, making it sufficiently complete.

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

Parameters2/5

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

Schema coverage is 33% (only idempotency_key described). The description reinforces idempotency_key usage ('Pass the same idempotency_key when retrying') but adds no meaning for conversation_id or client_id, leaving the low coverage unaddressed.

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+resource: 'Links a conversation to a contact'. Distinguishes itself from siblings by describing the operation's semantics (folding threads, saving email address) rather than just naming the action. No explicit alternative named, but the operation is unique enough.

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?

Implies when to use: linking a conversation to a contact. Provides a retry instruction, but no explicit guidance on when to choose this over alternatives (e.g., merge_conversations) or when not to use it.

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

All Sergio by Serviche tools Inspect

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

Need Help?