Skip to main content
Glama

read_quality_rule

Read-onlyIdempotent

Read a survey's response-quality rules (attention checks, minimum dwell time, impossible answer combinations, source review defaults): all of them, one kind, or one rule by id. These are the rules; the flags they produce come with read_responses.

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": "read_quality_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idNoReturn a single rule by id
rule_kindNoFilter to one rule type
survey_idYesSurvey UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the read-only, idempotent annotations, the description clarifies an important behavioral boundary: this returns rule definitions, not the flags those rules produce. It does not explain not-found or empty-result behavior, but that is a minor omission for this straightforward read operation.

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 compact sentences front-load the resource, rule types, and supported access patterns, then give the essential sibling distinction. Every phrase contributes useful selection or invocation information without repetition.

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?

Together with the fully described schema, safety annotations, and output schema, the description supplies nearly everything needed to select and invoke this simple read tool. The only notable invocation ambiguity is how the two optional selectors interact when both are provided.

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?

Although schema coverage is 100%, the description adds plain-language meaning to enum values such as dwell_time and impossible_combination and clearly maps the optional parameters to retrieval by kind or id. It leaves unresolved whether rule_id and rule_kind can be supplied together and, if so, which takes precedence.

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—reading a survey's response-quality rules—and enumerates the supported rule kinds and retrieval scopes. It also distinguishes these rules from the flags available through the sibling read_responses tool.

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?

It tells the agent to use this tool for all rules, one rule kind, or a rule selected by id. The explicit direction to read_responses for generated flags provides clear alternative-tool guidance and prevents confusing configuration with results.

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