Skip to main content
Glama

面灵AI 面试助手

search_interview_questions

Read-only

按公司、岗位或关键词搜索真实面试中被问过的题目,按出现频次排序,返回第一页(每行一题)。参考解析需在面灵AI 网站登录后查看。

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": "search_interview_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNohot = 出现次数最多,recent = 最近被问到hot
companyNo公司名
keywordNo题目关键词
positionNo岗位,如「后端开发」「算法」

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real value on top: results are ordered by occurrence frequency, only the first page is returned (a meaningful scope limit), output is one question per line, and reference analyses require site login. Minor imprecision: it says results are frequency-sorted while the schema allows sort=recent, but this is a default description rather than a contradiction.

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?

Two compact clauses, front-loaded with the search scope, followed by the result shape and the login caveat. Every part contributes; no filler sentences.

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?

With no output schema, the description still tells the agent what comes back (first page only, one question per line) and warns about the login requirement for analyses. Combined with fully documented parameters and annotations, an agent has enough to call it correctly; only pagination limits beyond 'first page' are left implicit.

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%, including the hot/recent enum with its own explanation, so the schema carries the parameter burden. The description merely restates the facets and the frequency default, adding no syntax, format, or combination semantics 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 states a specific verb+resource (search real interview questions that were actually asked) plus the facets available (company, position, keyword) and the default ordering. It is clearly distinct from sibling tools like list_related_questions or draw_questions, though it never names an alternative explicitly.

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 by listing the search facets, but there is no explicit when-to-use/when-not guidance and no routing to a sibling for related tasks (e.g. related questions or question drawing). The login note for reference analyses is the only conditional context provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources