Skip to main content
Glama

SinoAgriTech Crop & AgriTech

List SinoAgriTech Curated Topic Hubs & Briefings

list_topic_hubs
Read-only

List active research Topic Hubs and weekly empirical trend briefings in SinoAgriTech. 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 context by previewing what the hubs contain (briefs, methodology, benchmarks, institutes), which matters because there is no output schema. It says nothing about result count behavior beyond the default, pagination, or what an empty week looks like.

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 compact sentences, front-loaded with the verb and resource before the content preview. The trailing inventory of content types is slightly listy but still earns its place since no output schema exists. Nothing is redundant.

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 read-only, two-optional-parameter listing tool with full schema coverage, the description covers purpose, scope, and a preview of returned content. The remaining gap is minor: it does not state ordering or what happens when week_id matches nothing.

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 fully documented with defaults and format examples. The description's only contribution is the implicit hint that results are organized weekly; it does not explain how limit interacts with the week filter. Baseline 3 applies when the schema carries the load.

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 uses a specific verb ('List') plus two concrete resources: active research Topic Hubs and weekly empirical trend briefings. It also previews the content types (executive briefs, methodology highlights, benchmark targets, institutes). It stops short of explicitly contrasting itself with search_research or get_paper_dossier, so sibling differentiation is left to inference.

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?

There is no explicit when-to-use/when-not guidance and no named alternative, so it never tells the agent to prefer search_research for keyword lookups. However, words like 'active' and 'weekly' implicitly frame this as a browse-curated-content call rather than a search, which gives the agent some grounding.

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