Skip to main content
Glama

Избранные вопросы

get_favorite_questions
Read-onlyIdempotent

Возвращает библиотеку избранных вопросов аккаунта — вопросы, которые автор переиспользует в разных опросах. В каждой записи лежит снимок вопроса, готовый к передаче в update_quiz_widgets.

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_favorite_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by describing the shape of returned records (a snapshot of the question ready for update_quiz_widgets), which is meaningful given there is no output schema. It does not mention pagination, ordering, or empty-library behavior, keeping it at an adequate rather than rich level.

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, front-loaded with the purpose and followed by the return-shape note. Every sentence earns its place and nothing is redundant.

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 single-parameter read tool with no output schema, the description conveys what the tool returns (a library of reusable question snapshots) and how the output feeds into update_quiz_widgets. Only minor gaps remain, such as ordering or whether an empty library is possible.

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% and the single workspace_id parameter is already documented in-schema with a reference to workspace://list. The description adds no additional meaning about the parameter, so the 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?

States a specific verb and resource ('Возвращает библиотеку избранных вопросов аккаунта') and qualifies what a favorite question is ('вопросы, которые автор переиспользует в разных опросах'). An agent can distinguish this read tool from mutation siblings like save_favorite_question and delete_favorite_question, though those are not named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence implies the downstream workflow by saying each record is 'готовый к передаче в update_quiz_widgets', which gives implicit when-to-use context. However, there is no explicit statement of when to call this versus the sibling save/delete favorites operations, nor any exclusion.

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