Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_additional_party

Link an existing party as a secondary contact on an opportunity or project. Prevents duplicate links by confirming whether the party was already added.

Instructions

Link an existing party as an additional (secondary) party on an opportunity or project. The 'main' party is set via update_opportunity / update_project; this adds additional parties beyond the main one. Idempotent — re-adding a linked party is harmless. Response: {linked: true, alreadyLinked: false} on a fresh link, {linked: true, alreadyLinked: true} if the party was already linked (Capsule's 422 'already a contact' / 'already related' is caught internally and converted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesWhich entity has the additional-party links.
partyIdYesID of the party (person or organisation) to link as an additional party.
entityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / required
      Previous value: -[
-  "entity"
-]New value: +[
+  "entity",
+  "entityId",
+  "partyId"
+]
  2. Changed2 schema fields changedv2.1.2
    • changedInput schema / properties / entity / description
      Previous value: -"Which entity has the additional-party links. Use 'kases' for projects."New value: +"Which entity has the additional-party links."
    • changedInput schema / properties / entity / enum
      Previous value: -[
-  "opportunities",
-  "kases"
-]New value: +[
+  "opportunities",
+  "projects"
+]
  3. Addedv1.7.0
  4. Removedv1.6.2
  5. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses idempotency, the exact response shapes for fresh and repeated links, and that Capsule's 422 error is caught and converted internally. This is substantial behavioral context that helps an agent predict side effects and interpret results.

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?

The description is compact and front-loaded. Every sentence adds useful information: the action, the relationship to main-party setup, idempotency, and the response shape. No redundant or filler content is present.

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?

Given there is no output schema, the description does well to document the response behavior in detail. It also covers idempotency and error conversion, which are the main behavioral hazards. Combined with the schema's enum and parameter descriptions, the tool is adequately specified for 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?

The schema already describes 'entity' and 'partyId', and the description reinforces that the party must be existing and that the target is an opportunity or project. However, the required 'entityId' parameter is not described in either the schema or the description, leaving its meaning to be inferred from context.

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?

The description opens with a specific verb and resource: link an existing party as an additional secondary party on an opportunity or project. It also distinguishes this operation from setting the main party, which is handled by update_opportunity / update_project, so it is clearly differentiated from sibling tools.

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?

The description explicitly states where the main party is set via update_opportunity / update_project and clarifies that this tool adds additional parties beyond the main one. This gives the agent a clear decision rule for when to use this tool versus the relevant alternatives.

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

Deploy Server

Other Tools