Skip to main content
Glama
EQIQs

@eqiqs/mcp-server

Official
by EQIQs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Add a person

create_profile

Create a new person profile with optional traits like MBTI or DISC, enabling team tools and meeting prep.

Instructions

Add a new person to the user's workspace, optionally with traits already known (e.g. an MBTI type from a past assessment). Use invite_person instead when the person should take the assessment themselves. Returns the new profile id. Costs 1 unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name (required).
emailNoOptional email; used to match results if they later take the assessment.
eq_scoreNoOptional emotional-intelligence score 0-100.
disc_typeNoOptional DISC style: D, I, S, C or a blend such as DI.
mbti_typeNoOptional four-letter MBTI type, e.g. INTJ.
departmentNoOptional team or department, used by score_team, prep_meeting and suggest_lead.
date_of_birthNoOptional YYYY-MM-DD. Personal data: never used in business context.
enneagram_typeNoOptional Enneagram type 1-9, with wing if known, e.g. 3w2.
attachment_styleNoOptional. Personal data: never used in business context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changedv0.1.1
    • addedInput schema / properties / attachment_style / description
      Added value: +"Optional. Personal data: never used in business context."
    • addedInput schema / properties / attachment_style / maxLength
      Added value: +40
    • addedInput schema / properties / date_of_birth / description
      Added value: +"Optional YYYY-MM-DD. Personal data: never used in business context."
    • addedInput schema / properties / date_of_birth / format
      Added value: +"date"
    • addedInput schema / properties / department / description
      Added value: +"Optional team or department, used by score_team, prep_meeting and suggest_lead."
    • addedInput schema / properties / department / maxLength
      Added value: +120
    • addedInput schema / properties / disc_type / description
      Added value: +"Optional DISC style: D, I, S, C or a blend such as DI."
    • addedInput schema / properties / email / description
      Added value: +"Optional email; used to match results if they later take the assessment."
    • addedInput schema / properties / email / format
      Added value: +"email"
    • addedInput schema / properties / enneagram_type / description
      Added value: +"Optional Enneagram type 1-9, with wing if known, e.g. 3w2."
    • addedInput schema / properties / eq_score / description
      Added value: +"Optional emotional-intelligence score 0-100."
    • addedInput schema / properties / eq_score / maximum
      Added value: +100
    • addedInput schema / properties / eq_score / minimum
      Added value: +0
    • addedInput schema / properties / mbti_type / description
      Added value: +"Optional four-letter MBTI type, e.g. INTJ."
    • addedInput schema / properties / mbti_type / maxLength
      Added value: +4
    • addedInput schema / properties / name / description
      Added value: +"Full name (required)."
    • addedInput schema / properties / name / maxLength
      Added value: +120
    • addedInput schema / properties / name / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only signal that this is not read-only, not idempotent, and not destructive. The description goes further by disclosing the return value ('Returns the new profile id') and an operational cost ('Costs 1 unit'). It does not cover reversibility or permissions, but provides useful behavioral context beyond 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?

Three sentences carry the main action, the alternative, the return value, and the cost. There is no filler, and the most important decision-relevant information is front-loaded.

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 create tool with a well-described 9-parameter schema, the description supplies the missing operational details: the returned profile id and the per-call cost. It also resolves the main confusion with invite_person. An agent has enough to correctly select and invoke this tool.

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 parameter already has a meaningful description. The description only adds a general use-case note about pre-known traits like MBTI, which is helpful context but not new parameter-level semantics. 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 description states a specific action and resource: 'Add a new person to the user's workspace.' It also explicitly distinguishes itself from invite_person, naming the main sibling with a different purpose. The title 'Add a person' reinforces the same clear intent.

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?

The description gives an explicit alternative and the condition for using it: 'Use invite_person instead when the person should take the assessment themselves.' This tells an agent exactly when not to use create_profile, which is the key routing decision among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools