Skip to main content
Glama

Get Test

get_test
Read-only

Retrieve a test's details and all questions, including answers and images, to review or export assessment content.

Instructions

Detalle de un test y todas sus preguntas (con solución e imagen).

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value by disclosing payload content — questions including solutions and images — which tells the agent the response can be large and contains answer keys. It does not discuss size limits, pagination, or failure modes for invalid test_id.

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?

One short sentence with the core information front-loaded and no filler. It is terse to the point of under-specification rather than verbose, which is preferable to padding.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the read-only annotation covers the safety profile. What remains missing is where test_id comes from and what happens on a missing or invalid test, leaving the definition adequate but with clear gaps.

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% for the single parameter, so the description must compensate. It does not explain test_id at all (format, source, or behavior when it does not exist), but the parameter is a single, self-evidently named required integer ID, so the gap is modest.

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+resource ('Detalle de un test') and adds the important scope detail that it returns all questions with solutions and images. This distinguishes it from list_tests and export_test, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no mention of alternatives such as list_tests or export_test, and no stated prerequisite (e.g., that test_id comes from list_tests). Usage must be inferred from the word 'Detalle' alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.