QuestionPunk

Display Logic List

display_logic_list

Read-onlyIdempotent

List a survey's display logic: one container per question that has any (targetSurveyItemId), with its groups and rules and their ids. Read it before adding, changing or deleting logic, and to explain why a question is hidden.

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

Input Schema

Name	Required	Description	Default
`surveyId`	Yes	Survey ID to get display logic for

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds a genuinely useful behavioral detail: only questions that actually have logic produce a container, which tells the agent that absent questions imply no logic rather than an error. It stops short of describing ordering or nesting depth.

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, front-loaded with purpose, no filler. The parenthetical "(targetSurveyItemId)" interrupts the sentence slightly and could be folded in more cleanly, but nothing is wasted.

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

Completeness4/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-format detail is not required, and annotations cover the safety profile. For a one-parameter read tool, the description plus structured data give an agent everything needed to call it and interpret the result.

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 single surveyId parameter is fully documented in the schema with format uuid, so the description carries no additional parameter burden. The one descriptive term it introduces (targetSurveyItemId) refers to output content, not the input parameter, so it adds no input semantics. 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 ("List a survey's display logic") and immediately describes the returned structure: one container per question carrying logic, with groups, rules, and their ids. This clearly separates it from the display_logic_* mutators and the question_* siblings.

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?

"Read it before adding, changing or deleting logic" gives an explicit precondition for the create/update/delete siblings, and "to explain why a question is hidden" names a second concrete use case. It does not name the specific sibling tools, which keeps it a 4 rather than a 5.

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

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

Resources

Need Help?