EQIQs

Add a person

create_profile

Add a new person to the user's workspace with a name and, optionally, type labels the person has shared themselves (MBTI, DISC, Enneagram). Birthdate, attachment style and scores are never saved here — use invite_person so the person answers for themselves. Returns the new profile id. Costs 1 unit.

Input Schema

Name	Required	Description
`name`	Yes	Full name (required).
`email`	No	Optional email; used to match results if they later take the assessment.
`eq_score`	No	Ignored and never saved — scores come only from the person's own assessment.
`disc_type`	No	Optional DISC style (D, I, S, C or a blend), only if the person shared it themselves.
`mbti_type`	No	Optional four-letter MBTI type, only if the person shared it themselves.
`department`	No	Optional team or department, used by score_team, prep_meeting and suggest_lead.
`date_of_birth`	No	Ignored and never saved — the person adds this themselves via invite_person.
`enneagram_type`	No	Optional Enneagram type 1-9, only if the person shared it themselves.
`attachment_style`	No	Ignored and never saved — the person adds this themselves via invite_person.

Output Schema

Name	Required	Description	Default
`profile`	No	The newly created profile.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 30, 2026

changedInput schema / properties / attachment_style / description

Previous value: -"Optional. Personal data: never used in business context."New value: +"Ignored and never saved — the person adds this themselves via invite_person."

removedInput schema / properties / attachment_style / maxLength
```
Removed value: -40
```

changedInput schema / properties / date_of_birth / description

Previous value: -"Optional YYYY-MM-DD. Personal data: never used in business context."New value: +"Ignored and never saved — the person adds this themselves via invite_person."

removedInput schema / properties / date_of_birth / format
```
Removed value: -"date"
```

changedInput schema / properties / disc_type / description

Previous value: -"Optional DISC style: D, I, S, C or a blend such as DI."New value: +"Optional DISC style (D, I, S, C or a blend), only if the person shared it themselves."

changedInput schema / properties / enneagram_type / description

Previous value: -"Optional Enneagram type 1-9, with wing if known, e.g. 3w2."New value: +"Optional Enneagram type 1-9, only if the person shared it themselves."

changedInput schema / properties / eq_score / description

Previous value: -"Optional emotional-intelligence score 0-100."New value: +"Ignored and never saved — scores come only from the person's own assessment."

removedInput schema / properties / eq_score / maximum
```
Removed value: -100
```
removedInput schema / properties / eq_score / minimum
```
Removed value: -0
```

changedInput schema / properties / mbti_type / description

Previous value: -"Optional four-letter MBTI type, e.g. INTJ."New value: +"Optional four-letter MBTI type, only if the person shared it themselves."

Changed1 schema field changedSep 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "profile": {
+      "additionalProperties": {},
+      "description": "The newly created profile.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed18 schema fields changedSep 25, 2026
- 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
```
First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that certain accepted parameters are silently ignored and discarded, states the return value (new profile id), and gives a cost of 1 unit. The silent-drop behavior is a non-obvious trait an agent could easily get wrong.

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?

Four short sentences, front-loaded with the action and its allowed fields, then the exclusion rule, then return value and cost. Every sentence carries decision-relevant information with no padding.

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?

With an output schema present, return details need not be expanded, and the description still summarizes the id. For a non-idempotent create with 9 parameters, it covers creation scope, exclusions, alternative tool, cost and result — nothing essential 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 already 100%, so the baseline is 3; the description earns a notch more by grouping the accepted type labels (MBTI, DISC, Enneagram) and flagging the trap parameters that are accepted but never persisted. It leaves email and department unmentioned, though the schema covers them.

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?

Names a specific verb and resource ('Add a new person to the user's workspace') and immediately scopes what can and cannot be set. It also names the sibling it is not (invite_person), so an agent can distinguish the two without reading schemas.

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 states the negative case — birthdate, attachment style and scores are never saved here — and points to invite_person as the correct alternative when the person must self-report. That is a clear when-to-use/when-not-to-use routing rule.

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

All EQIQs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?