Skip to main content
Glama

Import Test

import_test

Creates a new unpublished draft test in a course from a test.json bundle, validating the import format and reporting problems to fix before retry.

Instructions

Crea un test nuevo (BORRADOR, no publicado) en un curso a partir de un test.json.

Lee antes orbits://docs/import-format. Si ok=false con problems, corrígelos y reintenta.

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": {
      "course_id": "<course_id>",
      "test": "<test>"
    },
    "name": "import_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
testYescontenido de test.json (formatVersion 1).
imagesNoruta en el bundle (p. ej. "images/q1.png") -> contenido del archivo en base64.
course_idYescurso destino.
image_pathsNo(solo instalación local) ruta en el bundle (p. ej. "images/q1.png") -> ruta local del archivo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the non-obvious fact that the import produces an unpublished draft, that a format doc must be consulted first, and that failures return ok=false with a problems list to correct and retry. It does not mention permission requirements, what happens on re-import/duplicates, or how images are attached, which keeps it from a 5.

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: what it does, the prerequisite read, and the failure path. Front-loaded with the action and the draft status, with no redundant restatement of the schema.

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 four-parameter tool with a nested arbitrary payload and an output schema, the description covers the essential workflow and references the return contract (ok/problems) without duplicating it. Gaps remain around the image parameters and any preconditions on course_id, but nothing an agent needs to make the call is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns more by pointing to orbits://docs/import-format as the authoritative definition of the `test` payload structure, which the schema only gestures at ('formatVersion 1'). It still says nothing about the distinction between `images` (base64) and `image_paths` (local install only).

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 ('Crea un test nuevo') plus the two scoping facts that matter: it is created as a DRAFT ('BORRADOR, no publicado') and it lands in a course from a test.json. That already separates it from export_test, get_test and list_tests without the agent opening any schema.

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

Usage Guidelines4/5

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

Gives a clear precondition ('Lee antes orbits://docs/import-format') and an explicit error-handling loop ('Si ok=false con problems, corrígelos y reintenta'). What is missing is any when-not guidance or named alternative (e.g. when to edit an existing test instead of importing a new one), so it stops short of a 5.

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