Sautikit

desk_create_contact

Creates a new SautiDesk customer contact.

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

Input Schema

Name	Required	Description
`name`	Yes	contact display name
`email`	No	primary email address
`notes`	No	contact notes
`phone`	No	primary E.164 phone number
`purpose`	No	Required on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
`organization`	No	company or organization name

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only supply the generic safe-mutation profile (destructiveHint=false, openWorldHint=false); the description adds no behavioral context of its own. It does not say what happens if a contact with the same email or phone already exists, whether the call is idempotent, what identifier is returned, or what permissions are needed.

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?

A single front-loaded sentence with no filler and nothing redundant. It is clean but sits right at the edge of being too thin for a six-parameter write operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create/mutation tool with six parameters and no output schema, the description omits the duplicate-handling rule, the return value, and any follow-up expectations. The rich 'purpose' parameter description does some of the work, but the tool-level definition is too sparse for correct invocation.

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 every one of the six parameters already carries its own explanation, including the mandatory 'purpose' field. The description adds no meaning beyond the schema, which makes the baseline 3 correct here.

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 gives a specific verb and resource ('Creates a new SautiDesk customer contact'), which is unambiguous on its own. It stops short of distinguishing this from adjacent siblings such as add_dialer_contacts, add_broadcast_contacts, or desk_merge_contacts, which also bring contacts into the system through different paths.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this versus the contact-import siblings or desk_update_contact, and no stated prerequisites or exclusions. The agent must infer usage entirely from the tool name and the one-line purpose statement.

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

All Sautikit 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?