Minds: Synthetic Market Research

List Audience Segmentations

list_formations

Read-onlyIdempotent

Lists visible Audience segmentations with Formation/subgroup IDs and counts for respondent filters. Ready counts are final. Paged (limit 1–100, default 100); pagination.nextOffset continues while hasMore.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_formations"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`offset`	No
`groupId`	No	Legacy alias for audienceId. Accepted for compatibility.
`groupName`	No	Legacy alias for audienceName. Accepted for compatibility.
`audienceId`	No	Audience ID (UUID). Preferred when known.
`audienceName`	No	Audience name: exact or partial (case-insensitive), with a fuzzy fallback for typos.

Output Schema

Name	Required	Description
`audienceId`	No	Audience whose visible segmentations were listed.
`formations`	No	Visible segmentations: id, name, status, source, dimensionKey, and subgroups with id, label, memberCount and isAuxiliary. Ready Formation/subgroup IDs identify respondent filters.
`pagination`	No	Page metadata: total, limit, offset, hasMore and nextOffset.
`totalCount`	No	Total number of visible segmentations across all pages.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent safety profile, but the description adds meaning they don't: results are scoped to 'visible' segmentations and 'Ready counts are final', which signals that non-ready counts may still change. It also discloses the paging model and how to continue via pagination.nextOffset.

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?

Three tightly packed sentences, front-loaded with purpose and then pagination. No wasted wording, though the 'Formation/subgroup' and 'Ready counts' terminology is somewhat internal and could be clarified in the same space.

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?

An output schema exists so return shape needn't be described; the description covers scoping, count finality, and pagination, which are the non-obvious behaviors. What's missing is the relationship to list_audiences and filter precedence among audienceId/audienceName/legacy aliases.

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 67%, and the schema already documents the legacy groupId/groupName aliases. The description adds the limit bounds and default plus the offset-continuation mechanism, which is useful but does not explain the audienceId/audienceName filtering or how they interact with the legacy aliases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: lists visible Audience segmentations with Formation/subgroup IDs and counts. That distinguishes it from list_audiences by what it returns, though it never names the sibling explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by 'for respondent filters'. There is no statement of when to call this versus list_audiences or how it relates to audience/study workflows.

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

All Minds: Synthetic Market Research 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.