Minds: Synthetic Market Research

List Research Methods

list_research_methods

Read-onlyIdempotent

Lists the research-method catalog without changing or running methods. For availability, report every label and the exact count in each availabilitySummary group. Use methods for complexity and fallbacks; advanced methods can require opt-in.

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_research_methods"
  }
}

Input Schema

Name	Required	Description	Default
`includePlanned`	No	Set to false to exclude planned methods. Experimental methods are still listed and cannot run. Only entries with executable: true can run.

Output Schema

Name	Required	Description	Default
`methods`	No	Research methods and whether each can run.
`availabilitySummary`	No	Complete answer-ready availability groups for the returned catalog. Use the supplied counts and include every label when reporting which methods can run.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / includePlanned / description

Previous value: -"Include experimental and planned methods that cannot run yet. Availability is dynamic; only entries with executable:true can run."New value: +"Set to false to exclude planned methods. Experimental methods are still listed and cannot run. Only entries with executable: true can run."

addedOutput schema / properties / availabilitySummary

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "executable": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "count": {
+                  "description": "Exact number of returned methods in this group, including zero. Use this count directly.",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "labels": {
+                  "anyOf": [
+                    {
+                      "items": {
+                        "type": "string"
+                      },
+                      "type": "array"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ],
+                  "description": "Complete list of exact catalog labels in this group. Preserve every label in an availability overview."
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "All returned methods with executable set to true, including advanced methods that require explicit opt-in."
+        },
+        "notExecutable": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "count": {
+                  "description": "Exact number of returned methods in this group, including zero. Use this count directly.",
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "labels": {
+                  "anyOf": [
+                    {
+                      "items": {
+                        "type": "string"
+                      },
+                      "type": "array"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ],
+                  "description": "Complete list of exact catalog labels in this group. Preserve every label in an availability overview."
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "All returned methods that cannot run. This group can be empty."
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Complete answer-ready availability groups for the returned catalog. Use the supplied counts and include every label when reporting which methods can run."
+}

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / includePlanned / description

Previous value: -"Include methods that are currently planned/non-executable so the model can explain framework compatibility. Availability is dynamic; only entries with executable:true can run."New value: +"Include experimental and planned methods that cannot run yet. Availability is dynamic; only entries with executable:true can run."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "methods": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Research methods and whether each can run."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / includePlanned / description

Previous value: -"Include planned methods such as Conjoint so the model can explain framework compatibility. Only entries with executable:true can run."New value: +"Include methods that are currently planned/non-executable so the model can explain framework compatibility. Availability is dynamic; only entries with executable:true can run."

First observedJul 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'without changing or running methods' is largely a restatement. The description does add genuinely new context beyond the annotations: advanced methods may require opt-in, and methods carry complexity and fallback information. It says nothing about result size or paging behavior for the catalog listing.

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 short sentences, front-loaded with the scope statement. The middle sentence about reporting every label and exact count in each availabilitySummary group is output-handling guidance that earns its place because it targets an output-schema field an agent might otherwise summarize loosely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, annotations fully cover the safety profile, and there is only one optional parameter with complete schema documentation. The description additionally flags the opt-in requirement and one output field to report faithfully, leaving no material gap for correct invocation.

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 100% and the single parameter includePlanned is fully documented in the schema, including the executable:true caveat. The description never mentions the parameter, so it neither adds nor detracts beyond the baseline.

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 the research-method catalog') and adds a negative scope clause ('without changing or running methods') that separates it from any execution-style tool. The resource is clearly distinct from the audience/study/formation list siblings, though it does not explicitly name an alternative.

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?

Gives downstream guidance ('Use methods for complexity and fallbacks; advanced methods can require opt-in') which implies why an agent would consult the catalog, but never states when to call this versus another listing tool or when calling it is unnecessary.

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.

List Research Methods

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources