Skip to main content
Glama

SinoTechIntel Materials & Tech

List SinoTechIntel Curated Topic Hubs & Briefings

list_topic_hubs
Read-only

List active research Topic Hubs and weekly empirical trend briefings in SinoTechIntel. 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.6/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 the safety profile is covered. The description adds genuine value by enumerating what the returned hubs contain (executive briefs, methodology highlights, benchmark targets, institutes), which partially substitutes for the absent output schema, but it says nothing about ordering, what 'active' means, or pagination behavior.

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 with the core purpose front-loaded and no filler. The second sentence earns its place because no output schema exists and the return contents would otherwise be unknown.

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

Completeness5/5

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

For a simple read-only, zero-required-parameter listing tool with full schema coverage, the description covers purpose, scope, and result content. Nothing an agent needs in order to call it correctly is missing.

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 and week_id are already documented with defaults, bounds, and an ISO-week example. The description adds no format or semantics beyond the schema; the phrase 'weekly ... briefings' only loosely echoes the week_id filter.

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 verb and resource: listing active Topic Hubs and weekly empirical trend briefings in SinoTechIntel. It is distinguishable from siblings like search_research or get_paper_dossier because it describes a curated browse/listing operation, though it never explicitly contrasts itself with those tools.

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: the word 'List' plus 'active' signals a discovery/browsing scenario, and no conditions, exclusions, or alternatives are stated. An agent can infer that this is the browse path rather than the search path, but nothing in the text confirms or denies that.

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