Minds: Synthetic Market Research

List Research Methods

list_research_methods

Read-onlyIdempotent

Reads the fixed Minds research-method catalog in one operation, including availability, complexity and fallback method. includePlanned only filters the returned catalog. It does not create, configure or execute a method, and the catalog cannot be edited through this tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`includePlanned`	No	Include experimental and planned methods that cannot run yet. Availability is dynamic; only entries with executable:true can run.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`methods`	No	Research methods and whether each can run.

Schema Changelog

Changes observed during successful MCP inspections.

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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond them: the catalog is fixed, includePlanned has no side effects beyond filtering, and mutation is impossible through this tool. It stops short of describing result ordering or size, hence not a 5.

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?

Two tight sentences, front-loaded with what the tool returns followed by the boundary conditions. Every clause earns its place; nothing is repeated from the schema or annotations.

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, so return-value detail is not required here, and annotations cover the safety profile. For a zero-required-parameter read tool, the description supplies everything an agent needs: scope, what it returns, and what it cannot do.

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% and the single parameter is already well documented in the schema, including the executable:true caveat. The description's "includePlanned only filters the returned catalog" adds only a mild reinforcement of that parameter's semantics, so the baseline 3 applies.

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?

States a specific verb and resource ("Reads the fixed Minds research-method catalog") and enumerates the returned fields (availability, complexity, fallback method). No sibling tool covers a method catalog, and the description explicitly rules out the confusable write operations (create/configure/execute), so an agent can place it instantly.

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?

Clearly frames the tool as a read-only catalog lookup and states what it does NOT do ("does not create, configure or execute a method, and the catalog cannot be edited through this tool"). It gives exclusions but no named alternative for related tasks, which is acceptable since no sibling overlaps.

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.