Skip to main content
Glama

SinoAILab AI & Robotics

List SinoAILab Curated Topic Hubs & Briefings

list_topic_hubs
Read-only

List active research Topic Hubs and weekly empirical trend briefings in SinoAILab. Includes executive briefs, methodology highlights, benchmark targets, and key Chinese research institutes.

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_topic_hubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of hubs to return (default 10, max 20)
week_idNoOptional ISO week filter such as "2026-W47"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful return-content context (executive briefs, methodology highlights, benchmark targets, institutes), which matters since there is no output schema, but it says nothing about ordering, freshness, or whether omitting week_id returns the latest week.

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 sentences, front-loaded with the core action and scope; the second sentence efficiently enumerates what the hubs contain. The content list earns its place as the only description of return values, though it borders on enumeration padding.

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?

A zero-required-parameter read tool with fully documented parameters and a stated content preview is close to complete. The remaining gap is behavioral detail around default week selection and result ordering, which an agent would want when calling it without a week filter.

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 both limit (1-20, default 10) and week_id (ISO week format) are already fully documented. The description adds no additional meaning about how week_id interacts with the 'active' filter or what the limit applies to.

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?

Names a specific verb and resource: listing active research Topic Hubs plus weekly trend briefings in SinoAILab, with a preview of the bundled content. The resource is clearly distinct from the sibling set (paper dossiers, empirical tables, general search), though the description never explicitly contrasts itself with search_research.

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 only implied by the word 'List' and the 'active' qualifier — an agent can infer this is a browse/overview entry point. There is no explicit when-to-use, when-not-to-use, or named alternative to prefer for narrower lookups.

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