Skip to main content
Glama

Answer Typeza test questions

answer_test

Send the person's answers for one batch of a Typeza test begun with start_test, using its draft_id and key. answers maps each question code to 1 (statement_1 fits better) or 2 (statement_2 fits better). Returns status next_questions with the next batch or, once every question is answered, the result: status type_found with the Typeza type (name, slug, page, short description) and keep_url, or status choose_type with candidate types when the answers fit more than one equally. Answers are saved with every call, so a test can continue later: send empty answers to get the current batch back. Give the person keep_url: it opens the full result on typeza.ai and lets them save it to an account. For a signed-in person, a first result becomes their Typeza type; a retake keeps the type they have.

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": {
      "draft_id": "<draft_id>",
      "key": "<key>",
      "answers": "<answers>"
    },
    "name": "answer_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key start_test returned, passed back unchanged.
answersYesQuestion code to 1 (statement_1 fits better) or 2 (statement_2 fits better). Send {} to get the current batch back.
draft_idYesThe draft_id start_test returned.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses non-obvious behavior: answers are persisted on every call so a test can resume, and for a signed-in person the first result becomes their saved Typeza type while a retake preserves the existing one. That account-level side effect is exactly the kind of consequence an agent would not infer from the structured fields.

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?

It is front-loaded with the action and prerequisities, and nearly every sentence carries information (resumption, three return statuses, keep_url, account persistence). It is dense as a single block and repeats the status vocabulary that the output schema also enumerates, costing a little efficiency.

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

Completeness5/5

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

For a stateful multi-step quiz tool it covers prerequisites, idempotent-looking resumption, all terminal outcomes (type_found, choose_type), the keep_url follow-up, and account-level effects. Given an output schema exists, its return-value description is bonus rather than obligation, so nothing an agent needs is missing.

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 coverage is 100%, so the schema already documents draft_id, key, and the answers mapping including the {} behavior. The description restates the 1/2 statement-fit convention without adding format, ordering, or validation detail beyond the schema — a baseline 3 is appropriate.

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 sentence names a specific verb (send answers) and resource (one batch of a Typeza test), and ties itself to the start_test sibling by referencing its draft_id and key. An agent can tell this apart from start_test, choose_test_type, or get_my_type without opening a 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?

It states the prerequisite (a test begun with start_test) and describes an explicit secondary use case: sending empty answers to retrieve the current batch, which makes the tool usable for resuming. It does not spell out when-not-to-use or name an alternative for re-fetching a result, but the context for invocation is clear.

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