Skip to main content
Glama

SinoGreenTech Clean Energy

List SinoGreenTech Curated Topic Hubs & Briefings

list_topic_hubs
Read-only

List active research Topic Hubs and weekly empirical trend briefings in SinoGreenTech. 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

B3.2/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 and the bar is lower. The description adds that results cover 'active' hubs and 'weekly' briefings, hinting at recency scoping, but says nothing about ordering, pagination beyond the schema's limit, or what a returned hub record actually contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded and efficient. The second sentence is a content inventory ('executive briefs, methodology highlights, benchmark targets, and key Chinese research institutes') that reads ambiguously — it could be taken as returned fields or as filterable inputs, which is a mild source of confusion rather than pure waste.

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?

For a two-parameter, zero-required, read-only listing tool with no output schema, this is largely sufficient: the agent knows what it enumerates and that it is safe. The main residual gap is that, absent an output schema, the 'Includes...' sentence is the only hint at return shape and it is too vague to rely on.

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%, with limit and week_id both documented in-schema including the ISO week format and max 20. The description adds no meaning beyond that — it never mentions the week filter or the result cap — so 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?

States a specific verb and resource: 'List active research Topic Hubs and weekly empirical trend briefings in SinoGreenTech.' This is clearly a browsing/enumeration operation, which implicitly contrasts with siblings like search_research and get_paper_dossier. It stops short of naming or differentiating against any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all — nothing says whether to reach for this instead of search_research or get_paper_dossier, nor any prerequisite or exclusion. The only signal is the verb 'List', from which an agent must infer a discovery/browse use case.

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