Skip to main content
Glama

Minds: Synthetic Market Research

by ai.getminds
OverviewDiscussionsAdmin

List Study Drafts

list_study_drafts
Read-onlyIdempotent

Lists durable unfinished study drafts, or returns the complete saved planning state for one exact draft ID. Draft records are distinct from running or completed studies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftIdNoExact study draft ID to retrieve. Omit to list all resumable study drafts owned by the authenticated user.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNoThe requested draft, or null.
draftsNoResumable drafts.
totalCountNoNumber of drafts returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "draft": {
+      "description": "The requested draft, or null."
+    },
+    "drafts": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Resumable drafts."
+    },
+    "totalCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Number of drafts returned."
+    }
+  },
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / draftId / pattern
      Added value: +"^([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)$"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds genuine behavioral context beyond this: the dual-mode behavior (list-all vs single retrieve), the 'durable' qualifier distinguishing drafts from ephemeral states, and the scope of what is returned. This is valuable added context with no contradiction to the annotations.

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?

Two sentences with no filler; the primary listing purpose is front-loaded, and the second sentence clarifies the dual-mode behavior and scoping. Efficient and well-ordered, though it could be tighter still.

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

Completeness3/5

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

For a simple read tool with one optional parameter at 100% coverage, an output schema present, and annotations covering safety, the description is mostly adequate. The main gap is the lack of explicit routing to sibling tools (e.g., using list_studies for completed studies), which is only implied.

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%, so the baseline is 3. The description does add some parameter-linked meaning by explaining the behavioral branch: providing a draftId yields the complete saved planning state, while omitting it lists all drafts. This is modest value beyond the schema, not a full compensation, so 3 is appropriate.

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?

The description opens with a specific verb+resource ('Lists durable unfinished study drafts') and covers the second mode (returning the complete saved planning state for one exact draft ID). It differentiates drafts from running or completed studies, which conceptually separates it from the sibling list_studies, though it doesn't name 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?

The clause 'Draft records are distinct from running or completed studies' implies when to use this tool versus alternatives like list_studies or save_study_draft, but the guidance is implied rather than explicit. It does not name any sibling or give a clear when-not-to-use directive.

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 toolsInspect
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.

Resources