Skip to main content
Glama

list_related_questions

Read-only

列出与某道题相关的高频题(优先同标签,其次同岗位,按被问次数排序),每行一题。题目 ID 取自 search_interview_questions 等工具。

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": {
      "id": "<id>"
    },
    "name": "list_related_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes题目 ID
limitNo返回条数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, closed-world and non-destructive, so safety is covered. The description adds real behavioral context beyond that — the ranking precedence (tag before position, then frequency) and the one-question-per-line output shape. It says nothing about behavior when no related questions exist, but given the annotation coverage this is a reasonable, above-baseline disclosure.

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?

Two compact sentences: the first front-loads what is returned and how it is ordered, the second carries the ID-provenance constraint. No filler, and the parenthetical ranking rules are dense rather than verbose.

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 two-parameter read-only list tool with no output schema, the definition covers purpose, ordering, output shape and input provenance. Only the empty-result case and the effective cap on returned rows are left implicit, which is minor given the schema's limit bounds.

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%, so both parameters (id, limit) are already documented with defaults and bounds. The description's one contribution is provenance for the id — that it must be obtained from search_interview_questions and similar tools — which is useful cross-tool context the schema cannot express, but 'limit' gets no additional meaning.

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 and resource (list related high-frequency questions for a given question) and even the ranking logic (same tag first, then same position, ordered by ask count). It is clearly different from the search tools it references, though it never explicitly contrasts itself with search_interview_questions as an alternative retrieval mode.

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?

It establishes a clear precondition: the question ID must come from search_interview_questions or similar tools, which tells an agent this is a follow-up/second-hop tool rather than an entry point. It does not state when NOT to use it (e.g., when no seed ID exists) or name a true alternative, so it stops short of a 5.

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