Skip to main content
Glama

Calculate Big Five scores

calculate_personality_scores
Read-onlyIdempotent

Use this when the user has answered all 50 items of the IPIP Big-Five Factor Markers test (answers 1-5 in item order) and wants their personality test scores. Returns raw scores (10-50) for Extraversion, Agreeableness, Conscientiousness, Emotional Stability and Intellect/Imagination, an approximate percentile, a low/average/high band with a plain-language description, a share card (SVG) and a share page link. Reverse-keyed items are scored automatically. Does not diagnose anything and is not for hiring decisions. Do not use for other questionnaires (MBTI, DISC, Enneagram) or with invented answers.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional first name or nickname for the share card, e.g. Alex. Leave empty for an anonymous card.
answersNoRequired. The 50 answers in item order, each 1-5 (1 very inaccurate ... 5 very accurate), e.g. [4,2,4,2,4,2,5,2,4,2, ...]. A string like "4,2,4,2,...", "4242..." or a numbered list "1: 4, 2: 2, ..." also works. Use null for an unanswered item.

Output Schema

NameRequiredDescriptionDefault
nameYes
domainsYes
downloadsYes
norm_noteYes
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds value beyond that: it discloses that reverse-keyed items are scored automatically, that output includes a share card and percentile band, and that it does not diagnose or serve hiring decisions.

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?

Front-loaded with the trigger condition, then return shape, then exclusions. Slightly dense but every sentence carries signal – no filler or repetition.

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 read-only scoring tool with a rich output schema and 100% param coverage, the description fills the remaining gaps: input expectation (50 items), scoring behavior (reverse-keying), and scope limits (no diagnosis, not for other tests). 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 description coverage is 100%, so both parameters (name, answers) are already documented with formats and examples. The description adds only that answers are 'in item order', which is largely redundant with the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource: computes Big Five scores from 50 IPIP answers, and enumerates the five returned traits. It is clearly distinguishable from siblings show_personality_test (which would present the test) and compare_personality_scores (which would compare results).

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?

Explicit trigger ('when the user has answered all 50 items ... and wants their scores') plus explicit exclusions ('Do not use for other questionnaires (MBTI, DISC, Enneagram) or with invented answers'). Both when-to-use and when-not-to-use are named.

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