Skip to main content
Glama
Sign In
@interviewsage/mcp

@interviewsage/mcp

by gowing111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

holland_assessment

Assess career interests with Holland's RIASEC model. Get 60 questions to complete, then submit answers to receive a three-letter code and full interpretive report.

Instructions

霍兰德职业兴趣测评（免费，规则计算）。不传 answers 时下发 60 道题；提交 60 题答案后返回三字母职业代码与完整解读报告。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "holland_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersNo60 题答案数组；留空则只下发题目

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden and does it well: it states the tool is free, uses deterministic rule-based calculation, and defines what happens in each mode based on whether answers are provided. It does not discuss partial answer sets, but schema constraints already cover the 60-item limit and score range.

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 a single compact sentence with no filler. The primary rule is front-loaded, and the conditional behavior is stated efficiently.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter tool with no output schema, the description covers how to start, how to complete, and what result format to expect. The only notable gap is explicit handling of incomplete answer sets, but the schema's maxItems constraint partially mitigates this.

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, but the description adds value by linking the presence or absence of the answers parameter to completely different outputs. It also clarifies that a full submission of 60 answers is what triggers the career code and report.

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 names a specific resource (Holland career interest assessment) and defines a clear two-mode behavior: return 60 questions when answers are absent, or return a three-letter code and full report when 60 answers are submitted. This clearly distinguishes it from the sibling resume, interview, and search tools.

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 makes invocation context explicit: call without answers to fetch the question set, call with answers to obtain the scored interpretation. It does not explicitly name alternatives, but the sibling tools are in clearly different domains, so no exclusion is strictly necessary.

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