Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_party_opportunities

Read-only

Retrieve opportunities linked to one party. Get answers to 'what deals do we have with X?' without listing every opportunity; include optional related details in one round-trip.

Instructions

List opportunities linked to a given party. Returns the same record shape as get_opportunity, filtered to one party — use this to answer 'what deals do we have with X?' without enumerating all opportunities. Accepts optional embed (e.g. 'tags,fields') to include those in one round-trip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
embedNoComma-separated embeds. Valid tokens: tags, fields, party, milestone, missingImportantFields.
partyIdYes
perPageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / required
      Added value: +[
+  "partyId"
+]
  2. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / embed
      Added value: +{
+  "description": "Comma-separated embeds. Valid tokens: tags, fields, party, milestone, missingImportantFields.",
+  "type": "string"
+}
  3. Addedv1.7.0
  4. Removedv1.6.2
  5. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral detail beyond annotations: the returned records match get_opportunity's shape, results are filtered by party, and embed enables including related data in one round-trip. This is meaningful context for an agent.

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?

Three sentences, each earning its place: the core action, the output shape and filtering behavior, and the embed capability with an example. The main purpose is front-loaded and there is no filler or repetition.

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 list tool with no output schema, referencing get_opportunity's record shape is a strong substitute for documenting return fields. The embed option and pagination parameters are at least recognizable from the schema. Some detail about pagination behavior or result limits could improve completeness, but the core invocation context is covered.

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 coverage is low at 25%, with only embed described in the schema. The description partially compensates by clarifying that partyId identifies the party and that embed accepts examples like 'tags,fields.' However, it does not explain page or perPage pagination semantics, leaving those to their schema defaults and names.

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 states a specific verb and resource: 'List opportunities linked to a given party.' It further clarifies the scope by saying the result is 'filtered to one party,' which distinguishes it from broader list/search opportunity tools. Naming get_opportunity for record shape also anchors the tool's expected output.

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 gives a clear use case: answer 'what deals do we have with X?' without enumerating all opportunities. This is strong context, though it does not explicitly name the alternative tool for enumerating all opportunities or exclude cases where search/filter opportunities would be better.

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