Minds: Synthetic Market Research

Get Audience Limits

get_audience_limits

Read-onlyIdempotent

Returns the authenticated account's current plan (planName, as the app names it), its Audience size allowance (per-Audience cap including any team or contract allowance, customSizeMax, per-mode ceilings) and the synthetic responses left, read live; it supersedes limits stated elsewhere. Sample sizes the plan allows: up to customSizeMax Minds per Audience, or several Audiences in one Study for a larger sample, each costing one response per Mind per question.

automaticSizingCeiling bounds the size the server picks when memberCount is omitted; explicitCountCeiling is the stated size above which a deeper mode builds it (only "balanced", on plans with one); otherwise memberCap alone bounds a stated size. Sizes are per Audience for the account and team named, not a reservation.

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": "get_audience_limits"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Report only this creation mode. Omit to see every mode.

Output Schema

Name	Required	Description
`planName`	No	The plan name the customer sees in the app. Use it, not the tier key in `plan`.
`responses`	No	Synthetic responses left for the account (`remaining`, `perMonth`, both -1 when unlimited, `renewsAt`); null when the balance could not be read.
`creationModes`	No	Audience creation modes and their limits, when a mode was requested.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / planName

Added value: +{
+  "description": "The plan name the customer sees in the app. Use it, not the tier key in `plan`.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / responses

Added value: +{
+  "description": "Synthetic responses left for the account (`remaining`, `perMonth`, both -1 when unlimited, `renewsAt`); null when the balance could not be read."
+}

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "creationModes": {
+      "description": "Audience creation modes and their limits, when a mode was requested."
+    }
+  },
+  "type": "object"
+}

AddedSep 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real behavior: limits are live, they override stated limits elsewhere, how the various ceilings govern auto vs. explicit sizing, and that sizes are per-Audience for the account/team named and not a reservation. This is substantive context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, but the middle paragraph is dense and heavily qualified (nested ceiling jargon, mode caveats), making it harder to parse than necessary for a simple read-only limits query.

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?

Because an output schema exists, the return values need not be re-explained; nevertheless the description covers the scoping (account/team, not a reservation), the ceilings, and mode behavior, leaving little ambiguity about what the agent will get. It is essentially complete for this tool.

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 description coverage is 100% for the single 'mode' enum parameter, so the schema already documents its purpose and omission behavior. The description adds partial semantics by referencing per-mode ceilings and a 'balanced' deeper mode, but does not clarify each enum value, so it only modestly exceeds the schema baseline.

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+resource: it returns the authenticated account's plan name, per-Audience size caps (customSizeMax, ceilings), and remaining synthetic responses, read live. This is clearly distinct from sibling list/creation tools and an agent can identify it as the limits-lookup tool immediately.

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?

It gives meaningful routing context by stating the values are 'read live' and that it 'supersedes limits stated elsewhere', steering the agent to trust this tool over other sources. It stops short of explicitly naming sibling alternatives or exclusions, but the context for when to call it is clear.

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.