Skip to main content
Glama
EQIQs

@eqiqs/mcp-server

Official
by EQIQs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get a person's profile

get_profile
Read-onlyIdempotent

Retrieve a complete 21-framework personality profile for a saved person using profile ID, email, or name. View results per framework with plain-language labels, strengths, and working-style notes.

Instructions

Return the full 21-framework read for one saved person: results per framework with plain-language labels, strengths, and working-style notes. Provide exactly one of profile_id, email or name. Read-only; costs 1 unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFull name. Ambiguous names return a list to choose from rather than a guess.
emailNoThe person's exact email.
contextNoRelationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include them.business
profile_idNoProfile id from list_profiles (preferred).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / context / default
      Added value: +"business"
    • changedInput schema / properties / context / description
      Previous value: -"Relationship context. Business (default) withholds personal-life signals: love language, attachment style, date of birth."New value: +"Relationship context that sets framework weighting. 'business' (default) is work-safe and withholds personal-life signals (love language, attachment style, date of birth); the other contexts include them."
    • addedInput schema / properties / email / description
      Added value: +"The person's exact email."
    • addedInput schema / properties / email / format
      Added value: +"email"
    • addedInput schema / properties / name / description
      Added value: +"Full name. Ambiguous names return a list to choose from rather than a guess."
    • addedInput schema / properties / profile_id / description
      Added value: +"Profile id from list_profiles (preferred)."
  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 already declare readOnlyHint and idempotentHint, so no contradiction exists. The description adds useful behavioral context beyond annotations, notably 'costs 1 unit' and the exact shape of the returned profile data. It does not elaborate on error behavior, but that is not required at this level.

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?

The description is two compact sentences with high information density. Output contents, identifier constraint, read-only nature, and cost are all front-loaded without wasted words.

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 no output schema, the description covers the return format clearly. The schema covers parameter semantics, especially the context enum and its privacy-related behavior, and annotations cover the safety profile. Nothing essential for correct invocation 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 100%, so the baseline is 3. The description adds meaningful constraint not expressed in the schema: exactly one of profile_id, email, or name must be provided. This is valuable because all parameters are optional in the schema and could otherwise be misused.

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 uses a specific verb ('Return') and a specific resource ('the full 21-framework read for one saved person'), and names the output contents: labels, strengths, and working-style notes. This clearly distinguishes it from sibling tools like list_profiles and get_my_profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear usage guidance: 'Provide exactly one of profile_id, email or name.' It also signals the tool is for one saved person, implying it is not for listing profiles or retrieving the caller's own profile, though it does not explicitly name alternatives or exclusions.

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