Skip to main content
Glama

Тест с вопросами

get_test
Read-onlyIdempotent

Тест целиком: порог зачёта, число попыток и вопросы по порядку. У каждого вопроса тип (one, many, text, number, open), варианты с отметкой верного либо верный текст. Владельцу и методисту — любой тест школы; остальным — только тест, стоящий в их курсах, и без верных ответов (is_correct, correct_text): стоять в курсе автора тест начинает от одной вставки номера в его урок.

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": {
      "test_id": "<test_id>"
    },
    "name": "get_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing role-dependent output redaction (is_correct and correct_text are stripped for non-owners) — a trait no annotation can express. It loses a point for the final sentence about how a test becomes 'in the author's course' via a single number insertion, which is cryptic and leaves the exact access boundary hard to predict.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the payload contents, then question shape, then permissions — a sensible order with little filler. The closing sentence is dense and grammatically tangled, costing clarity for the space it takes.

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?

There is no output schema, so the description carries the full burden of describing return values and does it well, including the conditional omission of correct answers. It falls short only on failure modes — no mention of what happens when the test is missing or the caller lacks access.

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 0% with a single integer test_id, so the description must compensate and does so only implicitly by framing the call as fetching one whole test. It never states where a test_id comes from (lesson, course, or list) or what happens for an id the caller cannot access, which is the notable gap given the access rules it describes.

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 opening line names a specific verb+resource and enumerates exactly what is returned: pass threshold, attempt count, and questions in order. It also enumerates the per-question shape (type one/many/text/number/open, options with correctness marks or correct text), so an agent knows precisely what this fetches versus create_test or get_lesson.

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?

Usage is implied by the description of contents rather than stated: there is no explicit 'use this when...' clause and no named alternative for other retrieval needs. What is given is conditional access guidance (owner/methodologist vs. everyone else), which shapes expectations but does not route the agent between sibling tools.

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