Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

filter_parties

Read-only

Filter parties by structured conditions: date ranges, tags, fields. Use for 'most recent client' or 'parties added this week'; combine conditions with AND and pick highest ID for newest.

Instructions

Filter parties by structured conditions (date ranges, tags, fields). Use this — not search_parties — for questions like 'most recent client', 'parties added this week', 'parties tagged VIP'. Capsule's API does not support ad-hoc sort, but for 'most recent X' you can filter by a date field (e.g. {field: 'addedOn', operator: 'is within last', value: 30}) and pick the highest-id row from the result — Capsule IDs are monotonic, so newest id = newest record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
embedNoComma-separated embeds. Valid tokens: tags, fields, organisation, missingImportantFields.
perPageNo
conditionsYesArray of filter conditions. All conditions are ANDed together. To get newest records, use a date condition like {field: 'addedOn', operator: 'is within last', value: 7} and pick the highest-id row from the result (Capsule IDs are monotonic).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.0
    • removedInput schema / properties / conditions / items / properties / value / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / conditions / items / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean",
+  "null"
+]
  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. Changed1 schema field 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."
  4. Addedv1.7.0
  5. Removedv1.6.2
  6. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds valuable behavioral context beyond annotations: the API does not support ad-hoc sort, Capsule IDs are monotonic, and the recommended workaround for 'most recent X' queries. This helps the agent predict result semantics accurately.

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 three dense sentences with no filler. The purpose is front-loaded, routing guidance follows, and the sort workaround is delivered efficiently with a concrete example. Every sentence earns its place.

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 filtering tool with no output schema, the description covers the essential use cases, limitations, and workaround strategy. It doesn't explain pagination or response shape, but those are largely inferable from the schema and the tool's role as a filter operation. The main gap is minimal and non-critical.

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?

The description adds meaningful semantic guidance beyond the schema by showing an actual condition object for date-range filtering and explaining how to derive the newest record. Given the schema already documents field/operator/value options thoroughly, the description supplements rather than repeats, which compensates reasonably for the moderate schema coverage.

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 'Filter parties by structured conditions (date ranges, tags, fields)', a clear verb-resource-mechanism statement. It also explicitly contrasts itself with search_parties, making the tool's purpose and differentiation immediately obvious.

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?

It directly says 'Use this — not search_parties — for questions like...' and provides concrete example queries. This is explicit when-to-use guidance with a named alternative, leaving no ambiguity about tool selection.

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