Capable

Link contact to account

add_account_contact

Destructive

Link a contact to an account with a role from the workspace's account_contacts.role values (seed defaults: champion / economic_buyer / decision_maker / user / blocker / influencer / csm_primary). Use is_primary_champion=true to mark the single primary champion (at most one per account; setting it auto-clears any previous primary). Distinct from opportunity_contacts — account_contacts persist across the customer relationship even when no opportunity is open. Resolve account_id + contact_id with search_* first — never invent ids.

When to use: When you learn someone's role at a customer. Set is_primary_champion=true for the single most important advocate.

Example: Add Sarah Chen as the primary champion at Acme.

Input Schema

Name	Required	Description
`role`	Yes	Defaults: champion \| economic_buyer \| decision_maker \| user \| blocker \| influencer \| csm_primary. A workspace admin may rename or add values — see the live set in propose_updates' workspace.enum_values, or an admin's describe_schema.
`notes`	No	Free-text context for this link (e.g. how the person relates to the account), stored on the account_contacts row; re-linking without it clears any stored note.
`account_id`	Yes	A uuid.
`contact_id`	Yes	A uuid.
`is_primary_champion`	No	Boolean (true/false).

Output Schema

Name	Required	Description	Default
`created`	No
`account_contact`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

removedInput schema / properties / is_primary_champion / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / is_primary_champion / type

Added value: +[
+  "boolean",
+  "string",
+  "number"
+]

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed7 schema fields changedOct 19, 2026

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / additionalProperties
```
Removed value: -{}
```
removedOutput schema / properties / account_contact / additionalProperties
```
Removed value: -{}
```

removedOutput schema / properties / account_contact / properties / account_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)$"

removedOutput schema / properties / account_contact / properties / contact_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)$"

removedOutput schema / properties / account_contact / properties / notes / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / account_contact / properties / notes / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the mutation profile is known. The description adds real behavioral value beyond that: the at-most-one primary champion invariant and that setting it auto-clears any previous primary. What it doesn't disclose is the destructive side of overwriting an existing link (e.g. what happens to a prior role/notes on re-link), which for a destructive-hinted tool would be worth one sentence.

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 and side effect, then cleanly sectioned into 'When to use' and 'Example'. Slightly redundant where the seed role values are repeated verbatim from the role parameter's schema description.

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

Completeness5/5

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

An output schema exists, so return values need no explanation. For a 5-param mutation the description covers the action, the uniqueness invariant, id resolution preconditions, terminology vs. opportunity_contacts, and a worked example — nothing an agent needs to call it correctly is missing.

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 semantics the schema does not: it names the seed role vocabulary and explains the uniqueness/auto-clear rule for is_primary_champion, which is a constraint rather than a type. The role list is somewhat duplicated from the schema, which caps it below 5.

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+resource ('Link a contact to an account with a role') and explicitly distinguishes itself from the opportunity_contacts concept, which is the most likely confusion point. An agent can tell what this creates and where it lives without opening the 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?

Explicit 'When to use: When you learn someone's role at a customer', plus the qualifier for is_primary_champion, plus a precondition ('Resolve account_id + contact_id with search_* first — never invent ids'). It also supplies a concrete example, leaving nothing to inference.

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

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