Skip to main content
Glama

Minds: Synthetic Market Research

Delete Study Template

delete_study_template
Destructive

Only for saved Study templates; it cannot delete Studies, Audiences, Minds or answers. Permanently deletes one template the authenticated user owns; Studies and drafts already created from it are unaffected.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "templateId": "<templateId>"
    },
    "name": "delete_study_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesTemplate to delete permanently. Owner only.

Output Schema

NameRequiredDescriptionDefault
dataNoDeletion acknowledgement: { success: true }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive annotation, the description adds that deletion is permanent, restricted to templates owned by the authenticated user, and does not cascade to Studies or drafts created from the template. These are meaningful behavioral details for a destructive tool.

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 tightly written sentences. The scope limitation is front-loaded, followed by the deletion effect and non-cascade behavior, with no wasted words.

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?

For a single-parameter destructive tool with full annotations and an output schema, the description covers purpose, exclusions, ownership, permanence, and downstream effects. Nothing essential is missing.

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 parameter already documents that it is the template to delete permanently and is owner-only. The description reinforces ownership but adds no syntax or format detail beyond the schema, so 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?

The description uses a specific verb-resource pair ('Permanently deletes one template') and explicitly scopes it to saved Study templates. It also distinguishes the target from Studies, Audiences, Minds, and answers, making misuse unlikely.

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 clearly says this is only for saved Study templates and lists the resource types it cannot delete. This provides strong exclusions, though it does not name an alternative tool for those other deletion cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.