Skip to main content
Glama

set_design

Replace a survey dataset's design attributes and re-run validation checks. Edit the design returned by get_dataset to update names, levels, kinds, or price settings.

Instructions

CBC: replace the dataset's design (attributes with name, levels, kind categorical / linear; none; price) and re-run the checks. Start from the design get_dataset returns and edit it.

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": {
      "dataset_id": "<dataset_id>",
      "design": "<design>"
    },
    "name": "set_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
designYes
dataset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'replace' and 're-run the checks,' which indicates mutation and a side effect, but it does not explain whether replacement is full or partial, what permissions are required, what happens to existing design settings, or what the checks validate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core action, but the parenthetical listing is dense and ambiguous, and the 'CBC:' prefix is unexplained. It is concise but not fully clear in structure.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and a nested object parameter at 0% schema coverage, the description is too thin. It does not explain the design object's expected shape, the role of dataset_id, what the checks return, or failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the design parameter is a nested object with no field documentation. The parenthetical 'attributes with name, levels, kind categorical / linear; none; price' is cryptic and does not clearly map to the object's structure, while dataset_id is not described at all.

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 and resource: 'replace the dataset's design' and 're-run the checks.' It also distinguishes this tool from get_dataset by telling the agent to start from the design that get_dataset returns.

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 gives explicit workflow guidance: 'Start from the design get_dataset returns and edit it.' It does not name when-not-to-use conditions or alternatives beyond get_dataset, but the prerequisite is clear.

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