Skip to main content
Glama

Compare two Big Five profiles

compare_personality_scores
Read-onlyIdempotent

Use this when the user wants to compare two people's Big Five personality test results, e.g. friends, partners or siblings who both took the 50-item test. Takes each person's five raw scores (10-50) and returns per-trait differences (similar when 3 points or fewer apart), each person's percentile, a comparison card (SVG) and a comparison page. Describes differences only; it does not rate compatibility, predict relationships, or judge who is better. Do not use for hiring or team selection.

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": {
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "compare_personality_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_aYesFirst person's raw scores, e.g. {"name":"Alex","extraversion":34,"agreeableness":41,"conscientiousness":29,"emotional_stability":30,"intellect_imagination":38}.
person_bYesSecond person's raw scores, e.g. {"name":"Sam","extraversion":22,"agreeableness":38,"conscientiousness":44,"emotional_stability":35,"intellect_imagination":31}.

Output Schema

NameRequiredDescriptionDefault
noteYes
person_aYes
person_bYes
downloadsYes
differencesYes
similar_countYes
largest_differenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavioral context the annotations cannot: the 3-point 'similar' threshold, that percentiles and an SVG comparison card and page are produced, and that it will not make compatibility judgments. It doesn't mention error behavior for out-of-range scores, which keeps it from a 5.

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 usage trigger, then the input format, then the outputs, then the exclusions. Four short sentences with no filler, and the most decision-relevant clause comes first.

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?

Despite nested objects and a rich output, the agent has everything needed: input shape, valid range, what is returned, and what the tool refuses to do. The output schema handles return structure, so the description isn't obliged to, yet it summarizes it usefully.

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% and each trait field already documents 'whole number 10-50' with an example, so the description's 'five raw scores (10-50)' is largely reiteration. Baseline 3 is appropriate; it adds no format or validation detail beyond 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 (compare two people's Big Five results) and immediately bounds the scope with 'Describes differences only; it does not rate compatibility, predict relationships, or judge who is better.' That cleanly separates it from calculate_personality_scores and show_personality_test.

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?

Explicitly names the trigger condition ('when the user wants to compare two people's... results, e.g. friends, partners or siblings who both took the 50-item test') and gives an explicit exclusion ('Do not use for hiring or team selection'). Both when-to-use and when-not-to-use are stated, so little is left to inference.

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