Skip to main content
Glama

edit_quality_rule

Create or update response-quality rules (attention check, dwell time, impossible combination, source review default). Use delete_quality_rule to remove one.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "edit_quality_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchNoRule fields — use get_mcp_schema module=quality_rule kind=<rule_kind>
createNoCreate a new response-quality rule
rule_idNoRule UUID (required for update; omit when using create)
rule_kindNoQuality rule type (required for update)
survey_idYesSurvey UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds no behavioral context beyond that: it does not say whether an update replaces or merges rule fields, whether existing rules can conflict, what permissions are needed, or that field shapes must be resolved via get_mcp_schema before writing.

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 short sentences with the purpose front-loaded and the sibling routing second; no filler, no restatement of the tool name, nothing to cut.

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 100% schema coverage, a nested create object, and an output schema, the description does not need to explain return values or field shapes. It covers the two operating modes at a high level, though it could have said one line about when to supply rule_id versus the create block, given this is a 5-parameter non-idempotent mutation.

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 description coverage is 100%, so the schema already documents survey_id, rule_id, rule_kind, the nested create object, and its enum values. The description only echoes the four rule-kind names, adding no syntax, format, or constraint detail beyond what the schema provides; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb pair ('Create or update') and a specific resource ('response-quality rules'), then enumerates the four rule kinds, so an agent immediately knows the domain. It does not explicitly distinguish itself from read_quality_rule, relying on the agent to infer that reads belong elsewhere, which keeps it short of a 5.

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 names the deletion alternative explicitly ('Use delete_quality_rule to remove one'), giving both an alternative and an exclusion. However, it gives no guidance on the create-vs-update decision itself, which is the main ambiguity for a combined tool (rule_id/rule_kind required for update, nested create object for creation) — that routing is left entirely to the schema.

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.

Resources