Skip to main content
Glama

Show Big Five personality test

show_personality_test
Read-onlyIdempotent

Use this when the user wants to take a personality test, a Big Five (five-factor, OCEAN) test, or a personality test for self-reflection, students, teens or couples. Shows the 50 public-domain IPIP Big-Five Factor Marker items in an interactive widget (one at a time, progress bar, back button); answers stay in the widget until the user submits, then they are scored with calculate_personality_scores. Also returns the item list and a browser link to take the same test. Does not score anything by itself. Do not use for MBTI/16-type, DISC or Enneagram tests, or to screen job candidates.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional first name or nickname to prefill for the result card, e.g. Alex.

Output Schema

NameRequiredDescriptionDefault
nameYes
itemsYes
scaleYes
test_pageYes
disclaimerYes
instructionsYes

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 readOnly/idempotent annotations, it discloses the interaction model (one item at a time, progress bar, back button), that answers remain in the widget until submission and are then scored by calculate_personality_scores, and that the tool does not score anything itself. That last statement is a genuinely valuable guard against misattributing results.

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?

Front-loads the trigger condition, then behavior, then exclusions in a tight sequence. Despite being a single dense paragraph, every clause carries decision-relevant information with no restatement of the title or schema.

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?

An output schema exists, so return values need no prose explanation; the description still mentions the item list and browser link as a courtesy. For a zero-required-parameter, read-only tool, nothing an agent needs to select or invoke it correctly 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?

The single optional parameter has 100% schema description coverage ("Optional first name or nickname to prefill for the result card, e.g. Alex"), so the schema already carries the meaning. The description adds nothing about the parameter, which is acceptable but not additive.

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: shows the 50 public-domain IPIP Big-Five Factor Marker items in an interactive widget. It also explicitly distinguishes itself from calculate_personality_scores, which does the scoring, so an agent can separate it from both siblings 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 Guidelines5/5

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

Opens with an explicit trigger ("Use this when the user wants to take a personality test..."), lists target audiences (self-reflection, students, teens, couples), and names concrete exclusions (MBTI/16-type, DISC, Enneagram, job-candidate screening). It also routes scoring to the sibling tool by name.

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