Skip to main content
Glama

Шаблоны аккаунта

get_workspace_templates
Read-onlyIdempotent

Показывает собственные шаблоны аккаунта — те опросы, которые сделали шаблонами через make_quiz_template. Это не общий каталог сервиса, его ищет search_quiz_templates. Найденный 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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_workspace_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько шаблонов вернуть, от 1 до 100. По умолчанию 20.
offsetNoСколько шаблонов пропустить.
workspace_idYesID workspace. Взять из workspace://list.
include_hiddenNotrue — вернуть и шаблоны, скрытые из галереи (set_template_hidden). У каждого шаблона есть is_template_hidden. По умолчанию false — как в галерее при создании опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_hidden
      Added value: +{
      +  "description": "true — вернуть и шаблоны, скрытые из галереи (set_template_hidden). У каждого шаблона есть is_template_hidden. По умолчанию false — как в галерее при создании опроса.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, closed-world), so the description rightly spends its words elsewhere: how a template comes into existence (made via make_quiz_template) and that its ids are interchangeable with catalog ids. It does not describe ordering or the shape of returned items, which leaves a small behavioral gap for a listing tool with no output schema.

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, each earning its place: identity, exclusion with the alternative named, and the follow-up action. The scoping statement is front-loaded before the sibling reference rather than buried.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with fully documented parameters, rich annotations, and no output schema, the description supplies everything needed to select and call it correctly, including provenance and the next step. No essential invocation detail is missing.

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% and each of the four parameters carries its own explanation (limit range and default 20, offset, workspace_id sourced from workspace://list, include_hidden default false with a pointer to set_template_hidden and is_template_hidden). The description adds no parameter-level meaning beyond that, so the 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 (shows the account's own templates) and immediately defines the scope: quizzes that were made into templates via make_quiz_template. It explicitly marks what this is NOT (the general catalog) and names the sibling that handles that case, so an agent can distinguish it from search_quiz_templates without opening either schema.

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?

Gives both when-to-use and when-not-to-use: use this for the workspace's own templates, use search_quiz_templates for the service catalog. It also completes the workflow by stating that the found id is passed to create_quiz_from_template exactly like a catalog id, which removes any doubt about downstream routing.

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