Skip to main content
Glama
Sign In

QuestionPunk

by io.github.questionpunk
OverviewDiscussionsAdmin

Display Logic Container Delete

display_logic_container_delete
Destructive

Remove all display logic from a question (its container with every group and rule), so the question always shows. Draft surveys only. displayLogicContainerId comes from display_logic_list. To change one condition, update or delete that rule instead.

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": {
      "displayLogicContainerId": "<displayLogicContainerId>",
      "surveyId": "<surveyId>"
    },
    "name": "display_logic_container_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
surveyIdYesThe survey ID
displayLogicContainerIdYesContainer ID to delete

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description's added value is in scope: it discloses that the entire container is removed, including every group and rule, not just one condition. The draft-only restriction is a genuine behavioral constraint the annotations do not express. It stops short of stating reversibility or error behavior on non-draft surveys.

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?

Three short sentences, front-loaded with the destructive scope, then the precondition, then the ID source and alternative. No redundant restatement of the tool name or schema text.

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?

With only two required parameters, full schema coverage, an output schema, and destructive annotations, the remaining burden is scope and precondition — both covered. An agent has everything needed to select and call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented and baseline would be 3. The description adds provenance the schema lacks by stating displayLogicContainerId comes from display_logic_list, which is actionable guidance an agent cannot derive from the schema.

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 ("Remove all display logic from a question") and clarifies the object is the container with every group and rule. The consequence ("so the question always shows") makes the effect unambiguous and separates it from the sibling rule/group delete tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit preconditions and exclusions: "Draft surveys only" rules out published surveys, and "To change one condition, update or delete that rule instead" names the alternative path. It also routes the agent to display_logic_list for the required ID.

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

All QuestionPunk 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