Skip to main content
Glama
Sign In
xiangguangyu-mcp-skills

xiangguangyu-mcp-skills

by XYG-LUNA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

skill_mbti-deep-analysis

Determine your MBTI personality type through a 28-question guided survey and receive an in-depth analysis report covering 16 personality types, cognitive functions, career tendencies, and personal growth advice.

Instructions

[mbti-deep-analysis] 通过28题引导式问卷判定MBTI四维度类型，生成包含16型人格解读、认知功能栈、职业倾向与成长建议的深度分析报告 (¥0.10/call)

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": {
      "query": "<query>"
    },
    "name": "skill_mbti-deep-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes用户输入内容 / user input for this skill

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions cost and number of questions but lacks details on data handling, limitations, or side effects.

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?

Single sentence with key information (purpose, method, cost). Efficient but could benefit from structure (e.g., separating description from cost).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 explains the report content (16 types, cognitive functions, etc.), which is sufficient for a simple tool. However, lacks behavioral and safety context.

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 coverage is 100% with one parameter. The description adds that query is user input, matching the schema. No additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is an MBTI deep analysis tool that determines four dimensions and generates a report. It is specific but does not differentiate from siblings, which are not MBTI-related.

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

Usage Guidelines3/5

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

Usage is implied for MBTI personality analysis, but there are no explicit when-to-use or when-not-to-use guidelines, nor alternatives mentioned.

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