Skip to main content
Glama

Поиск готовых опросов

search_quiz_templates
Read-onlyIdempotent

Ищет опрос в каталоге готовых: NPS, отзыв о заведении, заявка на услугу и прочие уже собраны. Каталог есть на русском и английском. Без query возвращает каталог целиком. Найденный template_id передаётся в create_quiz_from_template.

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": {
      "lang": "<lang>"
    },
    "name": "search_quiz_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesЯзык каталога: ru, en.
limitNoСколько шаблонов вернуть, от 1 до 100. По умолчанию 30.
queryNoЧто искать — по названию, описанию и меткам. Без него вернётся весь каталог.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / description
      Previous value: -"Язык каталога: ru или en."New value: +"Язык каталога: ru, en."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds context beyond that: the catalog exists in both Russian and English, an empty query returns everything, and the result feeds a downstream creation tool. It does not describe result shape or ordering, but with rich annotations that is a minor gap.

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 purpose, followed by the language and no-query behavior and then the handoff to the next tool. Nothing is redundant or padded.

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?

For a simple three-parameter read tool with full schema coverage, full annotations and no output schema, the description covers purpose, scope and downstream use. The only omission is what a result item contains besides template_id, which is a small gap for an agent that must pick a template.

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%, with each parameter documented including the limit range and default of 30 and query matching over title, description and tags. The description only restates that lang selects catalog language and that an absent query returns the whole catalog, adding little beyond the schema. Baseline 3 is appropriate.

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 specific action and resource — searching a catalog of pre-built quizzes — and names concrete catalog entries (NPS, review request, service request). It also clarifies the bilingual scope and the no-query behavior. It stops short of distinguishing itself explicitly from the sibling get_workspace_templates, which an agent could plausibly confuse it with.

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 a clear usage rule (no query returns the entire catalog) and a workflow handoff: the found template_id is passed to create_quiz_from_template. It does not state when to prefer this catalog over workspace-specific templates, so the exclusion case is left implicit.

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