Skip to main content
Glama

list_question_bank_companies

Read-only

题库中的公司热榜:按真实面试出现次数排序列出公司及其题目数,可按岗位或关键词筛选。公司名可作为 search_interview_questions、draw_questions 的 company 参数。未登录时只能查看前几页。

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

Input Schema

NameRequiredDescriptionDefault
pageNo页码,从 1 开始
keywordNo公司名关键词
positionNo岗位,如「后端开发」「算法」

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the ranking is by actual interview occurrence count, results include per-company question counts, and unauthenticated callers are limited to the first few pages. That auth/pagination constraint is the most useful disclosure, though return format details remain thin.

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?

Three short sentences, each earning its place: what is listed and how it is ordered, how the output feeds sibling tools, and the auth limitation. The core purpose is front-loaded with no filler.

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 carries the burden of describing returns and does so adequately (companies plus question counts, sorted by occurrence). The unauthenticated page limit is disclosed. Minor gap: it does not say how many pages or whether pagination metadata is returned, but an agent has enough to call it correctly.

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 description coverage is 100%, so page, keyword and position are already documented in the schema, and the description only restates that filtering is possible by position or keyword. It adds no syntax, matching behavior, or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: lists companies in the question bank ranked by real interview occurrence count, with question counts, filterable by position or keyword. This is clearly distinct from the sibling list_* tools and from search_interview_questions/draw_questions, which it explicitly references.

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?

Gives concrete downstream guidance: the returned company names can be passed as the company parameter to search_interview_questions and draw_questions, which tells the agent when this tool is a useful precursor. It does not state explicit exclusions or when not to use it, keeping it just 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