Skip to main content
Glama

Export Test

export_test
Read-only

Exports a test as an import-ready bundle, returning test.json and its image names; optionally saves the complete .zip with images to a local path.

Instructions

Exporta un test en formato de importación: devuelve test.json y los nombres de sus imágenes.

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": "export_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYestest a exportar.
save_zip_toNo(solo instalación local) ruta donde guardar el .zip completo (con imágenes).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, and the output schema covers the return shape, so the description's restatement of 'devuelve test.json y los nombres de sus imágenes' adds modest value. It says nothing about bundle size, missing image edge cases, or how the local-only zip path fails on hosted installs beyond what the schema already states.

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?

A single sentence with the core action and the returned artifacts front-loaded, and no filler. Nothing needs trimming and nothing important is buried.

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?

With an output schema and read-only annotation present, the description only needs to orient the agent, which it does by naming the export format and returned files. Minor omission: it doesn't state that the zip option is optional or describe the pairing with import_test for round-tripping.

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 100%, so both parameters (test_id and save_zip_to) are fully documented in the schema, including the local-installation caveat. The description adds no additional meaning about either parameter, which matches the baseline for fully covered schemas.

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?

The description gives a specific verb (exporta) and resource (un test) and pins the output format ('formato de importación': test.json plus image names), which implicitly separates it from get_test/list_tests and pairs it with import_test. It does not explicitly name a sibling, so it stops short of full differentiation.

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 only implied: the mention of an import format suggests exporting for migration or backup, and the schema notes save_zip_to is local-install only. There is no explicit statement of when to use this versus get_test or list_tests, nor any prerequisites or exclusions.

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