Skip to main content
Glama

Topic prominence analysis / 选题显示度分析

topic_prominence
Read-only

Topic prominence analysis / 选题显示度分析 | USE WHEN: the user asks whether a research direction is hot, influential or crowded | ALIASES: 显示度, 热不热, 影响力, 热度, 关注度, prominence, is this field hot | RETURNS: 显示度指标

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": {
      "topic": "<topic>"
    },
    "name": "topic_prominence"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes研究主题

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

A3.6/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 given. The description adds only 'RETURNS: 显示度指标', which restates the concept without saying what the metrics are, what corpus they draw from, or how cost/latency behaves. Given the annotations, this is adequate but thin.

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?

The pipe-delimited format front-loads purpose, trigger, aliases and output in a scannable way with no filler sentences. The bilingual repetition of the title and the untranslated 'RETURNS' field cost a little density but keep it short overall.

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

Completeness3/5

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

For a one-parameter, read-only analytical tool this is nearly sufficient, but the single sentence about output ('显示度指标') is opaque and there is no output schema to fall back on. An agent knows when to call it but not what it will receive, which is the one real gap.

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?

There is a single parameter with 100% schema description coverage ('topic' / '研究主题'), so the schema already documents it. The description adds no meaning about granularity, language, or expected phrasing of the topic string, so the baseline 3 applies.

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 definition names a specific verb/resource ('Topic prominence analysis', '选题显示度分析') and frames the question it answers: whether a research direction is 'hot, influential or crowded'. That framing separates it from siblings like topic_novelty or topic_feasibility, though no sibling is called out by name.

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 'USE WHEN:' clause gives an explicit trigger condition, and the ALIASES list ('热不热', 'is this field hot', 'prominence') broadens matchable phrasings. There is no when-not guidance and no named alternative, so the agent must infer which sibling to pick for adjacent questions.

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