Skip to main content
Glama

Favorite questions

get_favorite_questions
Read-onlyIdempotent

Returns the account library of favorite questions — the questions the author reuses across quizzes. Each item holds a snapshot of the question, ready to be put into 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_idYesWorkspace ID (from workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds context beyond that: items are snapshots (copies) rather than live references, and they are directly consumable by update_quiz_widgets — useful for reasoning about whether edits propagate back.

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 return subject, and every clause contributes — the definition of "favorite questions" and the snapshot/downstream-use note both earn their place. No filler or repetition of the title.

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 and full annotation coverage, the description supplies the one thing that could not be inferred: what an item actually contains (a snapshot of the question) and what it feeds into. Minor gap: it does not say whether the list is scoped/paginated or how many items typically come back.

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?

With one parameter at 100% schema description coverage, the schema already documents workspace_id and even its source (workspace://list). The description adds nothing 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 ("Returns") and resource ("account library of favorite questions"), and defines the concept inline as "questions the author reuses across quizzes," which separates it from save_favorite_question and delete_favorite_question. It stops short of explicitly naming those siblings as alternatives, but the read/mutate distinction is unambiguous.

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 clause "ready to be put into update_quiz_widgets" implies the downstream workflow for which this tool exists, which is genuine usage context. However, there is no explicit when-to-use/when-not-to-use statement and no guidance on alternatives such as get_quiz_structure or search_quiz_templates for pulling existing questions.

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.