QuestionPunk

Display Logic Rule Update Text

display_logic_rule_update_text

Destructive

Set the text a string condition matches (string_contains, string_does_not_contain, is_string_equal_to, is_string_not_equal_to, string_begins_with, string_ends_with), in one of the survey's languages. Draft surveys only. Call it after creating such a rule, which starts without text.

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": {
      "displayLogicRuleId": "<displayLogicRuleId>",
      "surveyId": "<surveyId>",
      "ruleCondition": "<ruleCondition>",
      "lang": "<lang>",
      "textFields": "<textFields>"
    },
    "name": "display_logic_rule_update_text"
  }
}

Input Schema

Name	Required	Description
`lang`	Yes	Language code (e.g., "en")
`surveyId`	Yes	The survey ID
`textFields`	Yes
`ruleCondition`	Yes	The rule condition type
`displayLogicRuleId`	Yes	Rule ID to update

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and readOnlyHint=false; the description adds two facts the annotations cannot convey: the mutation is limited to draft surveys and newly created rules have empty text, so the call is an initial assignment. It does not state what happens to previously set text, leaving the overwrite semantics implicit in 'Set'.

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 sentences with zero filler: the operation and its constraints lead, and the prerequisite and draft-only restriction follow immediately. Nothing is repeated from the title.

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?

With annotations covering the safety profile and an output schema present, the remaining burden is scope and sequencing, both of which are stated. The only gap is the absence of a pointer to the sibling update tool for non-text rule fields.

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 80%, so the schema carries most of the load. The description still adds meaning by tying ruleCondition to the text-bearing condition set and clarifying that lang selects one of the survey's languages, which is more than a restatement of the field name.

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 names a specific verb and target ('Set the text a string condition matches') and enumerates exactly which condition types accept text, so an agent can distinguish this from display_logic_rule_update and display_logic_rule_create at a glance.

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 timing guidance ('Call it after creating such a rule, which starts without text') and a hard scope restriction ('Draft surveys only'). It stops short of naming the sibling display_logic_rule_update as the alternative for non-text edits, but the applicable-condition list effectively routes the agent.

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?