Minds: Synthetic Market Research

Get Study Summary

get_study_summary

Returns or refreshes the semantic summary for a Study as Markdown plus flexible evidence blocks. Website, image, and video analyses retain heatmap-compatible block metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`force`	No	Regenerate even when the covered message range is unchanged.
`study`	No	Which Study to summarize. Omit entirely to use the active Study from this MCP session.
`length`	No		standard
`refresh`	No	Generate or refresh the summary instead of only reading the persisted summary.

Output Schema

TableJSON Schema

Name	Required	Description
`blocks`	No	Semantic summary blocks.
`studyId`	No	Summarized Study.
`summary`	No	Whole-Study summary.
`metadata`	No	Summary metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 22, 2026

removedInput schema / properties / panelId

Removed value: -{
-  "description": "Study ID (UUID; legacy wire field name: panelId). Omit both panelId and panelName only for the active Study from this MCP session.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}

removedInput schema / properties / panelName

Removed value: -{
-  "description": "Study name for fuzzy matching (legacy wire field name: panelName). Omit both panelName and panelId only for the active Study from this MCP session.",
-  "type": "string"
-}

addedInput schema / properties / study

Added value: +{
+  "description": "Which Study to summarize. Omit entirely to use the active Study from this MCP session.",
+  "properties": {
+    "id": {
+      "description": "Study ID (UUID). Omit with studyName to use the active Study.",
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "name": {
+      "description": "Study name to fuzzy-match among the newest 1,000 visible Studies; use studyId for older records. Omit with studyId to use the active Study.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedInput schema / properties / studyId

Removed value: -{
-  "description": "Study ID (UUID). Omit with studyName to use the active Study.",
-  "format": "uuid",
-  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
-  "type": "string"
-}

removedInput schema / properties / studyName

Removed value: -{
-  "description": "Study name to fuzzy-match among the newest 1,000 visible Studies; use studyId for older records. Omit with studyId to use the active Study.",
-  "type": "string"
-}

Changed1 schema field changedSep 22, 2026

changedInput schema / properties / studyName / description

Previous value: -"Study name for fuzzy matching. Omit with studyId to use the active Study."New value: +"Study name to fuzzy-match among the newest 1,000 visible Studies; use studyId for older records. Omit with studyId to use the active Study."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "blocks": {
+      "description": "Semantic summary blocks."
+    },
+    "metadata": {
+      "description": "Summary metadata."
+    },
+    "studyId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Summarized Study."
+    },
+    "summary": {
+      "description": "Whole-Study summary."
+    }
+  },
+  "type": "object"
+}

AddedAug 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the non-read-only nature is covered. The description adds that the summary retains heatmap-compatible block metadata for certain analyses, which is a useful output detail, but it doesn't disclose side effects beyond what 'refreshes' implies. Given the annotations, the description adds modest value without contradicting them.

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 a single, efficient sentence that front-loads the core action ('Returns or refreshes') and follows with the output format and a specific metadata detail. Every clause contributes meaning with no waste.

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?

Given the presence of an output schema and the annotations, the description covers the main purpose and output format. It doesn't explain the nuances of refresh vs force or study selection, but those are handled by the schema parameter descriptions. For a tool with four optional parameters, this is largely complete, with minor gaps around usage scenarios.

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 75% (three of four parameters have descriptions). The tool description does not elaborate on parameter meanings beyond the schema; it mentions output format but not parameter semantics. The length parameter lacks a description in the schema, and the description doesn't compensate. Since coverage is high, a baseline of 3 is appropriate.

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 clearly states the tool's purpose: it returns or refreshes the semantic summary for a Study, and specifies the output as Markdown plus flexible evidence blocks. It also notes a distinguishing detail about heatmap-compatible block metadata for website/image/video analyses, which helps differentiate it from sibling tools like get_study_status or list_studies.

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?

The description implies the tool is for retrieving or refreshing summaries, but does not explicitly state when to use it versus alternatives or when to set the refresh or force flags. It doesn't name any sibling tools or give conditions for choosing this tool over others. The usage context is implicit rather than explicit.

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.