Sliq

Create Deal

create_deal

A deal needs a person or a company (or both). Link someone Sliq already knows by id (query_people / query_companies), or pass new_person / new_company to add them. If the person already has an open deal this refuses and names it — update that deal instead, unless the user wants a second one (then pass allow_duplicate=true). The created deal, same shape as a query_deals row.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Deal name, e.g. "Acme - pilot". Usually the company name.
`notes`	No	Free-text notes.
`stage`	No	Pipeline stage by name or id (query_deals lists them). Default: the first stage.
`amount`	No	Deal value as a plain number, e.g. 12000.
`person_id`	No	The contact, as a query_people `id`.
`company_id`	No	The company, as a query_companies `id`.
`new_person`	No	A contact to add: name plus email or LinkedIn URL. Used instead of person_id.
`new_company`	No	A company to add: name plus domain. Used instead of company_id.
`on_behalf_of`	No	An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
`assignee_email`	No	The owner, an active teammate's email from list_teammates (not an invited one). Default: the user.
`allow_duplicate`	No	Create even if this person already has an open deal.
`expected_close_date`	No	YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / on_behalf_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}

AddedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds behavior beyond the annotations: duplicate-open-deal refusal with an error that names the existing deal, and dedup behavior for new_person/new_company ('an existing person with the same email/LinkedIn is reused, not duplicated'). Consistent with readOnlyHint=false and destructiveHint=false. Doesn't cover permissions or any limits, but the annotations already declare the safety profile.

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?

Front-loaded with the core action, then relationship linking and the duplicate edge case in priority order. Markup wrappers consume some space and the 'shows up on the Deals view for the whole team' sentence is the least load-bearing, but nothing is confusing.

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 12-parameter creation tool with no output schema, the description covers the key relational requirement, the duplicate path, and the return shape ('same shape as a query_deals row'). The many remaining parameters are fully documented in the schema, so the description is complete enough without duplicating them.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a real constraint not visible in the schema: a deal requires a person OR a company (or both), while the schema only marks name required. It also clarifies that person_id and new_person are mutually exclusive alternatives.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a deal in the user's CRM pipeline') and explains the underlying semantics ('this is how a person or company gets into the CRM') plus where it becomes visible. The agent can distinguish it from update_deal and query_deals without inspecting schemas.

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?

Gives explicit routing: link an existing person/company by id (via query_people / query_companies) or pass new_person / new_company. It also names the failure path ('if the person already has an open deal this refuses and names it — update that deal instead') and the escape hatch (allow_duplicate=true).

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

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