Skip to main content
Glama

Append Questions

append_questions

Adds new questions to an existing Orbits test by merging question sets from a test.json bundle, so agents can extend assessments without rebuilding them.

Instructions

Agrega preguntas a un test existente (mismo formato test.json; solo se leen formatVersion y questionSets).

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>",
      "test": "<test>"
    },
    "name": "append_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
testYescontenido de test.json.
imagesNoruta en el bundle -> contenido del archivo en base64.
test_idYestest destino.
image_pathsNo(solo instalación local) ruta en el bundle -> ruta local del archivo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but non-destructive write. The description adds genuinely useful behavior beyond that: only formatVersion and questionSets from the supplied test.json are consumed, so all other fields in the payload are silently ignored. It does not state what happens to duplicate or pre-existing questions, which is the main remaining behavioral unknown.

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?

A single sentence with the core action front-loaded and the non-obvious constraint in a compact parenthetical; no filler. It is on the terse side, but nothing in it is wasted.

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 full schema coverage, an output schema, and write annotations, the description supplies the one non-obvious behavioral fact an agent needs. Remaining gaps are merge semantics (deduplication of question IDs) and permission requirements, which are secondary but not trivial for a mutating append operation.

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 a point by clarifying that the 'test' object is only partially read (formatVersion and questionSets), which the schema does not say. It adds nothing about images or image_paths, but the schema already documents those.

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 and resource ('Agrega preguntas a un test existente'), which is more precise than the bare name. It implicitly distinguishes itself from siblings like import_test by requiring an existing test, but never names an alternative explicitly.

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 phrase 'a un test existente' tells the agent a target test must already exist, which separates it from test-creation tooling. There is no explicit when-to-use/when-not-to-use rule, no mention of import_test as the alternative for new tests, and no stated prerequisites such as publication state or required permissions.

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