Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_additional_parties

Read-only

List secondary parties like partners, consultants, or referrers on an opportunity or project. Provide the entity type and ID to retrieve these related contacts.

Instructions

List secondary party links on an opportunity or project. The 'main' party is on the entity itself (opportunity.party); additional parties are e.g. partners, consultants, or referrers also involved in the deal. Set entity to 'opportunities' or 'projects'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
embedNoComma-separated embeds. Valid tokens: tags, fields, organisation, missingImportantFields.
entityYesWhich entity has the additional-party links.
perPageNo
entityIdYesID of the opportunity or project.

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"
+]
  2. Changed1 schema field changedv2.2.0
    • changedInput schema / properties / embed / description
      Previous value: -"Comma-separated embeds. Valid tokens: tags, fields, missingImportantFields."New value: +"Comma-separated embeds. Valid tokens: tags, fields, organisation, missingImportantFields."
  3. Changed3 schema fields changedv2.1.2
    • changedInput schema / properties / embed / description
      Previous value: -"Comma-separated embeds, e.g. 'tags,fields'"New value: +"Comma-separated embeds. Valid tokens: tags, fields, missingImportantFields."
    • 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"
+]
  4. Addedv1.7.0
  5. Removedv1.6.2
  6. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint and destructiveHint annotations already establish this as a safe read operation, so the description does not need to re-state that. It adds useful conceptual context about what additional parties are, but it does not disclose pagination behavior, embed expansion, or response characteristics beyond the tool name.

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?

The description is compact and front-loaded with the core action, then adds a clarifying distinction and a direct instruction for the key parameter. No filler is present, though the third sentence partly repeats enum information already in the schema.

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

Completeness3/5

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

For a basic call, the required parameters and entity choices are sufficiently described, and annotations cover the safety profile. However, with no output schema, the tool does not explain what the returned secondary-party links look like, nor does it mention pagination defaults or embed usage, so an agent may lack enough detail for more advanced invocations.

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 documents entity, entityId, and embed. The description reinforces that entity selects the container and entityId identifies the specific opportunity/project, but it does not add meaning for page or perPage, which lack schema descriptions. With 60% schema coverage, the description only partially compensates for the undocumented parameters.

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 uses a specific verb and resource: 'List secondary party links on an opportunity or project.' It also clarifies the distinction from the main party and gives concrete examples (partners, consultants, referrers), which effectively differentiates this tool from related party-listing siblings.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool: when you need secondary party links on an opportunity or project, and it explains how to select the target entity via 'opportunities' or 'projects'. It does not explicitly name alternative tools, but the main-versus-additional distinction provides enough routing context.

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