Skip to main content
Glama

面灵AI 面试助手

get_product_overview

Read-only

面灵AI 的产品介绍:各产品线能做什么、支持哪些面试 / 笔试平台、客户端下载、价格页与帮助文档链接。回答用户关于面灵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": "get_product_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the scope of the returned content, which tells the agent what a call will surface. It says nothing about staleness or authority of the content relative to other sources, which matters for a documentation-style tool.

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?

A single content-enumeration clause plus one imperative sentence, with the routing instruction placed last as the action cue. No filler and nothing redundant for a zero-argument tool.

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 parameters, no output schema, and rich annotation coverage, the description carries most of the burden for return content, and it names the main sections the agent can expect. A brief note on freshness or how it relates to the knowledge-base tools would close the remaining gap.

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?

There are zero parameters, so the schema has nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that could mislead.

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 names a specific resource — a product overview for 面灵AI — and enumerates its contents (product lines, supported interview/written-exam platforms, client download, pricing page, help docs). That is far more concrete than a tautology. It stops short of differentiating from the likely-overlapping knowledge-base siblings (get_knowledge_base, get_official_knowledge_base).

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 gives an explicit routing rule: read this first before answering any question about 面灵AI. That is clear when-to-use guidance for an entry-point/overview tool. It does not state when another source (e.g., the knowledge-base tools) should be preferred instead, nor any exclusions.

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