Skip to main content
Glama

Start the Typeza test

start_test

Start the Typeza personality test in this conversation: 41 short questions, no account needed. Returns draft_id and key (keep both and pass them back unchanged), total, answered and the first batch of up to 7 questions. Each question has two statements: ask the person which one fits them better and wait for their answer. Never answer for them and do not show the codes. Then call answer_test with the batch's answers. language serves the statements in that language when a full translation exists, otherwise in English. The result is a Typeza type name, never a code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage code, for example en. Defaults to English.en

Output Schema

NameRequiredDescriptionDefault
keyYes
batchYes
totalYes
statusYes
answeredYes
draft_idYes
languageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only declare it is not read-only, not destructive, and closed-world), the description discloses that a draft_id and key are created and must be passed back unchanged, that a batch of up to 7 questions is returned, and imposes interaction rules (ask the person, wait, never answer for them, do not show codes). These are meaningful behavioral constraints an agent could not infer from the annotations.

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?

Purpose is front-loaded in the first clause, then return values, then the interaction protocol. Every sentence carries operational content; nothing is redundant filler.

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?

Given one optional parameter, an output schema, and simple annotations, the description covers what is returned, what must be retained, how to conduct the interaction, and what to call next. Nothing an agent needs to invoke and complete the flow is missing.

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% and the single `language` parameter is already documented, so the baseline is 3. The description adds real meaning: the statements are served in that language only when a full translation exists, otherwise English — a fallback rule not present in the schema.

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 ('Start the Typeza personality test in this conversation') plus scope details (41 short questions, no account needed). It is clearly distinguishable from siblings like answer_test, which it names as the continuation step.

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?

Explicitly says to start the test in this conversation and hands off to answer_test with the batch's answers, giving a clear flow. It does not, however, state exclusions such as what to do if the person already has a Typeza type (get_my_type) or wants a different test type (choose_test_type).

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